[Android] Crash when running release mode about maui HOT 18 OPEN

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Closed similar issues:

• Android Release Mode app crash during startup (#12165), similarity score: 0.80
• App crashes only in release mode and only when using AOT (#8337), similarity score: 0.76
• Fatal signal 6 (SIGABRT) crash on android release when forcing screen orientation (#22106), similarity score: 0.72
• Cannot start the application without starting it in debugging. (#13445), similarity score: 0.71

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

from maui.

You could comment on dotnet/runtime#103975 and ask if it is going back to .NET 8.

from maui.

Hi,

The AOT stuff is pretty glitched, try adding

<RunAOTCompilation>False</RunAOTCompilation>

to your .csproj for Android release builds, e.g.

<PropertyGroup Condition="'$(Configuration)|$(TargetFramework)|$(Platform)'=='Release|net8.0-android|AnyCPU'">
	<RunAOTCompilation>False</RunAOTCompilation>
</PropertyGroup>

from maui.

Hi,

The AOT stuff is pretty glitched, try adding

<RunAOTCompilation>False</RunAOTCompilation>

to your .csproj for Android release builds, e.g.

<PropertyGroup Condition="'$(Configuration)|$(TargetFramework)|$(Platform)'=='Release|net8.0-android|AnyCPU'">
	<RunAOTCompilation>False</RunAOTCompilation>
</PropertyGroup>

The problem is, I need aot, I've waited to update to maui from Xamarin, since IL stripping didn't work on maui and with .net 8 they've added support

from maui.

Just tried without AOT and still crashes

from maui.

Maybe it's not AOT then - but you mentioned IL stripping - maybe something there is being too aggressive? Maybe post your settings w.r.t. any IL stripping that's taking place.

from maui.

it was a combination of and IL stripping, is there a way to control IL removing?

from maui.

I'm encountering the same issue; disabling AOT didn't resolve it. I urgently need to create a release build. Is there a workaround available?

from maui.

It appears that dependency injection fails to work as expected in release mode; it crashes when a parameterless constructor is absent.

from maui.

It appears that dependency injection fails to work as expected in release mode; it crashes when a parameterless constructor is absent.

Have you figured out a workaround?

from maui.

@jonathanpeppers thoughts?

from maui.

In the end, the error was due to an incorrect definition in my XAML. The issue was that the actual error wasn't displayed anywhere. Correcting the XAML resolved the issue with Dependency Injection.

from maui.

There is a lack of information here, to know what went wrong.

@gabriel-kozma said:

it was a combination of and IL stripping, is there a way to control IL removing?

What was the setting that worked vs didn't work?

There is an issue related to the experimental $(AndroidStripILAfterAOT) setting, that should be fixed in .NET 9 now:

• dotnet/runtime#103975

from maui.

hi @jonathanpeppers just using IL stripping causes the app to crash, I could try the .net 9, but I would need to wait for production to release it?

Can this be back ported to .net 8?

I'll try here and report back

from maui.

Thank you @jonathanpeppers is there a way for me to add more logging in order to figure out how is breaking?

from maui.

I followed what @wagenheimer said and started looking, I'm not using XAML anymore, but I've had some code comments with the Xamarin.Forms xaml and it was this that was causing the problem with IL Stripping

another question I have @jonathanpeppers is were the empty dlls are stored on the release application? In xamarin they were stored at a file monodroidbundle which cointaned all dlls and I could verify that they were indeed stripped of their IL

from maui.

On Android, .NET assemblies are compressed into a single file that can be mmap'd in one call.

You can use either of these tools to inspect or pull them out of an .apk:

• https://github.com/dotnet/android/tree/main/tools/decompress-assemblies
• https://github.com/dotnet/android/tree/main/tools/assembly-store-reader

from maui.

Is this issue good to close now? Thanks!

from maui.