Xamarin.Essentials VS AutoMapper

This one was one of the most annoying bugs in MAUI, and I solved it with this workaround taken from IeuanWalker on this thread.

This behavior is by design as it enables SSO with web identities but can be problematic in situations like this. Unfortunately, this kind of sign-out isn't a well-supported scenario, but you can read a good discussion on GitHub about it here: https://github.com/xamarin/Essentials/issues/1223.

I don't know where you're seeing "xamarin/Essentials", but that's a repo for code used in writing cross-platform mobile applications. That message refers to this issue: https://github.com/xamarin/Essentials/pull/1457. It's something that was fixed in the project 7 months ago.

First, add the Xamarin.Essentials NuGet Package to your projects. If you're using MVVM (Like we're doing in this example), you'll ideally want to install the Xamarin.Essentials.Interfaces NuGet Package

In the guide they have a link to a sample controller which does this, so I borrowed the code from it and ended up with this authentication controller method:

Xamarin.Essential >=1.5.3

Fortunately for us Xamarin developers, the Xamarin team and the community have created the Xamarin Essentials library and one of its utilities is the MediaPicker, which abstracts from you the logic for taking a picture with the camera or getting an image from the storage. You can read the documentation for the Media picker here.

AutoMapper

The 13.0 Upgrade Guide page was created back in April, but there is no sign of the release yet.

The most well-know is probably AutoMapper, but it's not universally liked.

AutoMapper - well for automapping

When working with AutoMapper, we often bump into runtime errors due to invalid mapping configuration, such as this one:

What problems will resolve automapper?

If you are a fan of data mappers, you might want to enhance the implementation with additional extension methods. Here is an example for AutoMapper.

I'm wondering myself. Most mappers like https://automapper.org/ will make a best effort mapper automatically via introspection. If this is just a DSL/annotation suite that requires explicit, complete mapping implementations then this strikes me as a re-implementation of parts of kotlin in kotlin.