For us, a few weeks ago Azure DevOps randomly stopped processing GitHub webhooks, so merge commits didn't trigger builds anymore (and we're not the only ones, see https://developercommunity.visualstudio.com/content/problem/...). A fix for this issue still isn't deployed.
Just a few days ago the service connection to Azure suddenly stopped working with "401 CouldNotFetchAccessTokenForAzureStatusCode" which appeared when deploying to Azure AppService. We had to recreate the service connection to get it working again.
Recently we also wanted to move our Android builds to Azure DevOps but in the end the documentation was so confusing that we just used Bitrise instead.
I have a late-2016 Razer Blade and every time I compile something the fans spin up to aircraft-turbine levels of noise, it's ridiculous. I'm currently thinking of throwing the whole thing out and getting a Macbook Pro instead, because it's basically the loudest thing in our office.
That's what I really don't like about Azure.
They seem to have multiple differently named services that seem to basically do the same thing (Azure Service Bus/Azure Storage Queues is one example that comes to my mind)
Also, the Azure Portal is ridiculously bad and slow.
> The downside to this is that making a UI seems to even out your gained time--it's extremely messy and even complicated. Code that's valid in C# produces vague underwater bugs in Java code, which makes you keep hacking around until you find a working solution.
Interesting, I had the exact opposite experience, since the Java->C# mappings often reduce much of the boilerplate code that you have to write if you were using Java (e.g C# events, properties, etc..)
I also never came across any bugs in the mappings, but I can't say for sure that there aren't any.
Agreed, people seem to think Xamarin == Xamarin Forms, while the real power lies in shared business logic with native UIs, in my opinion.
Xamarin Forms may be useful for internal super-CRUD LOB apps that really are just a collection of input fields, but as soon as you do anything customer facing, you should be using the standard native UI approach.
Also +1 for ReactiveUI, it completely changed the way I build apps for the better.
Just a few days ago the service connection to Azure suddenly stopped working with "401 CouldNotFetchAccessTokenForAzureStatusCode" which appeared when deploying to Azure AppService. We had to recreate the service connection to get it working again.
Recently we also wanted to move our Android builds to Azure DevOps but in the end the documentation was so confusing that we just used Bitrise instead.