MvvmCross: Application gets stuck on splash screen in Release config with MvvmCross 8.0.2

πŸ› Bug Report

Application gets stuck on splash screen.

Expected behavior

Application gets navigated to the first view model.

Reproduction steps

Compile an iOS app with Release | iPhone configuration: SDK Version: 15.0 Linker behavior: Link Framework SDKs Only Supported architectures: ARMv7 + ARM64 HttpClient: Managed Debug information: None

  • Strip native debugging symbols
  • Enable optimizations

Either publish for TestFlight or locally launch on an iPhone device. The steps may not work on other projects.

Configuration

Version: 8.0.2

Platform:

  • πŸ“± iOS
  • πŸ€– Android
  • 🏁 WPF
  • 🌎 UWP
  • 🍎 MacOS
  • πŸ“Ί tvOS
  • πŸ’ Xamarin.Forms

Comment

That started after upgrading from 6.4.2 to 8.0.2. I also cannot debug it since with any debugging option enabled (still in Release configuration) the issue disappears. When I tried to downgrade to 7.1.2 the issue has gone as well.

I tried to find out the cause of the issue myself and found out that NavigateToFirstViewModel never finishes if awaited. If await is removed then the app crashes. I could be wrong it’s the key of the issue, just the maximum I could find myself.

About this issue

  • Original URL
  • State: open
  • Created 2 years ago
  • Reactions: 4
  • Comments: 17 (11 by maintainers)

Most upvoted comments

@ivmirx The workaround fixed the issue in both freezing and crashing projects. Thank you very much! @Cheesebaron take at look at the workaround please.

Probably can be temporarily solved with this workaround.

@entdark I guess your App is Ska?

Yes. It is. So why does it work fine in 7.1.2 if basically nothing got changed? And it works in Debug.

OK, turned out TipCalc.iOS sample was missing a LinkerPleaseInclude file to hint usage of stuff.

To be able to better debug this at your end. You can take a look at the device log with the Console app on your mac with the device attached. Here you should be able to see any exceptions thrown. I need more info to go from to be able to debug your issue.