Android: Debug works, release crashes

[bsdRuf]

Hello, I converted a Xamarin project to Maui. I was debugging on physical and emulated android devices. After being done with the debugging, I wanted to release my App to the devices to test the offline mode.

Any ideas why the release acts diffrent then the debug? (Android only tested on 12.0 /12.1 / 13)

[davidortinau]

This is usually a linker related issue where the release build optimization strips out unused code to make your app faster and smaller. In Xcode > Windows > Devices and Simulators, check your device log or open the console and reproduce the crash. That should give you an indication of what is happening and then you can resolve it.

[kj4bix]

I found that invalid resource bindings will run in debug but crash in release. I had the same issue finally checked every {StaticResouce } binding in the page and had an invalid one. Windows would throw an exception in debug, Android just ran, in release Android would crash. iOS didn't find them either, just ignored them.

[nll]

In Release mode the Pages / XAML files are compiled differently and some code maybe removed or transform differently.

Check the device log, install Android Studio and look at the Logcat, maybe the crash information will help

[gabsamples6]

That is the main cause of issues debug vs release invalid resource that works in debug not in release -the problem is that if enable xamlc compiling than hot reload won’t work

[DanTravison]

Are there any tools that can be run to detect this? I just hit this on android and ios and I had to pour through the android device log to track down the problem. I would expect this problem to lend itself to static analysis.