MvxApplication.Initialize runs on main thread

[NoahSurprenant]

MvxApplication.Initialize runs on main thread

[Cheesebaron]

It doesn't have anything to do with the naming change of MvxSplashScreenActivity to MvxStartActivity.

It is because instead of calling EnsureInitialized from the Splash/Start Activity this is now done through MvxAndroidApplication in OnCreate.

What is the issue you are having?

[NoahSurprenant]

Prior to version 9 of cross I had setup the splash screen to be able to add text to the screen. Mostly just to display the current environment name and announce any migrations being applied to the application's database. I am leaning towards removing this entirely now with 9 as it does not seem entirely feasible anymore. My other 'issue' is with initialize now being called on the main thread I am slightly concerning that it may be possible to get an ANR (App Not Responding) on android if for example the application was many versions behind and had many migrations to apply. Maybe my fear is slightly overblown or maybe there is a better place to be applying these migrations in the cross pipeline.

Also I did not mean to say that the renaming of the class changed the behavior of MvvmCross. :)

[NoahSurprenant]

Closing this issue. Recommended path forward is to not use MvxStartActivity to draw to the screen