[MAUI:Android:Release] Build crash on startup with GUID mismatch errors

[vsfeedback]

This issue has been moved from a ticket on Developer Community.

---

[severity:I'm unable to use this version] [regression] [worked-in:17.9.4]
Hi,

When upgrading some Nuget packages, the Android release build no longer runs.
Crash on startup, reports multiple errors in Device Log.

* Assertion at /_w/1/s/src/mono/mono/mini/aot-runtime.c:3810, condition ‘is_ok (error)' not met, function:decode_patch, module ‘FFimageTest.MAUI.dll.so’ is unusable (GUID of dependent assembly FFimageLoading.Maui doesn't match (expected '9753E4DA-4D73-4EED-9672-A1E4F942229A', got '182F2520-718C-4D1B-BBCF-84A5E0C25802')).

1. Clone https://github.com/EvgenyMuryshkin/FFImageTest/tree/ms NOTE: use branch "ms"
2. Open solution
3. Select Android, Release, build, and run on the connected device.
4. App from repo will run, list assemblies with versions.
5. Upgrage FFImageLoading to 1.2.0 and run on the device.
   app crashes on startup with an error in FFImageLoading.MAUI
6. Revert back to 1.1.9
7. Uncomment line in app.xaml.cs
   //Syncfusion.Licensing.SyncfusionLicenseProvider.RegisterLicense
   app crashes on startup with Syncfusion.License
8. Comment line with SyncFusion
9. Run the original version, it runs fine

I am not sure which version it worked, last working build was done on 13th of Apr 2024, probably 17.9.4

Thanks,
Regards,
Evgeny

---

Original Comments

Feedback Bot on 5/14/2024, 06:41 PM:

We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.

Paul Wang [MSFT] on 5/15/2024, 02:08 AM:

Thanks for your feedback! As shown in the screenshot below, I successfully build and debug to the Android phone, but I did not encounter the problem you mentioned. I followed the steps you described. Please help me confirm whether I missed any steps. Or where is the operation different from yours.

evgeny.muryshkin on 5/15/2024, 02:42 PM:

(private comment, text removed)

evgeny.muryshkin on 5/15/2024, 06:27 PM:

(private comment, text removed)

evgeny.muryshkin on 5/16/2024, 03:26 PM:

(private comment, text removed)

Paul Wang [MSFT] on 5/16/2024, 00:34 AM:

Yes, my steps are like this:

1. Clone project from https://github.com/EvgenyMuryshkin/FFImageTest/tree/ms
2. Upgrage FFImageLoading.Maui to 1.2.0.
3. Select Android platform, Release, build, and run on the connected device
4. Debug was successful without the error you described: “app crashes on startup with an error in FFImageLoading.MAUI”
5. Revert FFImageLoading.Maui back to 1.1.9
6. Uncomment line in app.xaml.cs
   //Syncfusion.Licensing.SyncfusionLicenseProvider.RegisterLicense
   7.Debug was also successful without the error you described: “app crashes on startup with Syncfusion.License”

Please correct me if any of my steps are different from yours. Can you provide screenshots or videos of the steps? Facilitate our further understanding and investigation? For your second question, I suggest you resubmit a new Feedback.

Feedback Bot on 5/17/2024, 01:38 AM:

We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.

Feedback Bot on 9/3/2024, 00:02 AM:

I detected that this issue hasn’t received a lot of activity, votes, or comments in the past 90 days. Based on this, the issues severity and affected area, it’s my experience that this issue is unlikely to get fixed. To improve the situation, consider following best practices for quality problem reports, and giving us more details on how this issue is impacting you.

[dellis1972]

@grendello @jonathanpeppers so I can repo this. I have no idea how to investigate it though. Looking at the logs of the "failing" build we pick up the new FFImageLoading.Maui assembly (1.2.0) it is linked and packaged. I'm adding the logs from my build

Logs.zip

[grendello]

@dellis1972 my first thought was that it's a packaging issue, but it's entirely possible the problem lies in the AOT compiler or even the MonoVM runtime. However, in the logs I noticed that there are some sources generated related to FFImageLoading - can it be that the assembly is rebuilt after AOT is done with it, because of that?