Tim Ahrentlov

Any recommendations on how fast to spin up a new 8.02 solution from the native template, and try things out? Currently it fails due to this issue.

> You can temporarily work around the issue by directly referencing Microsoft.Extensions.Logging 5.0.0. That's working for me on Android. And the runtime concerns of Jadebanks? Is the work around safe?

.NET 7 is not too far of, and WASM is going to be important in that release. Would be nice to experiment with blazor + realm soon :)

I like it! How easy will it be to extend or change the controls compared to the handler/renderer approach? It would also be nice to get a couple of navigation...

I like this idea - and the impact it could have. To have a `` component in which with all the drawn controls could be placed. One could use the...

In effect, what I am suggesting is a componentized design framework. Something that is for Blazor what [TailwindCss](https://tailwindcss.com/) is for HTML. It's not about doing away with CSS. It's about...

This is the only thing missing before I can move to the new version

This works for me: ``` .. FirebasePushNotificationManager.Initialize(options, false); Messaging.SharedInstance.AutoInitEnabled = true; Messaging.SharedInstance.Delegate = CrossFirebasePushNotification.Current as IMessagingDelegate; LoadApplication(new App(new iOSInitializer())); return base.FinishedLaunching(app, options); ```

+1

> The +1 and "have same issue" comments are not valuable, use reactions at the opening post. +1