Level set: I am a very experienced developer but on my first Xamarin Forms app.
My app is working at an alpha level in Android. I have not yet jumped through all of the iOS hoops. I initially ignored UWP because it is semi-unsupported. I subsequently decided to see if I could not build it in UWP also and I have been 98% successful. The app builds and runs and the pages appear correctly.
I ran into one unexplained anomaly. Basically I have an instance of a user-defined class initialized statically. I do an await on SecureStorage.GetAsync() and when I come back from the await, my class instance -- not referenced by the GetAsync() -- has become null. I hacked around that with if (instance == null) instance = new MyClass(); Fortunately I was able to do that because there was no values in the instance that I "needed" at that point in the logic.
I am now hitting another unexplained anomaly. I have not fully investigated but I seem to have code again with await SecureStorage.GetAsync() that seems to fail normally but work if I step through it with the debugger -- which is pretty frustrating! (This is code that works without issue on Android.)
So ... can someone tell me if I am just looking for frustrations and banging my head against the wall trying to use Xamarin Forms UWP ... or if there is something specific different that I need to be aware of ... or ... ?
VS 2019 Community 16.9.4 on Windows Pro 64-bit. Nothing real special in the app. Using SecureStorage, System.Security.Cryptography and System.Linq. No Crypto calls yet at the point of the problems I describe above.