Issues Building Android Release version MAUI

[Pmr-precure]

Hi,

We cant build our release version. Here is our config:

Not sure whats going on. If we remove the package then we got no issues. Hope you can help.

[Pmr-precure]

And of cause if we disable R8 then it runs fine.

[ksidirop-laerdal]

We've run some tests based on your feedback:

• We run a sample MAUI app with the settings you indicated in the .csproj and we could replicate the error you're seeing.

• Rebuilding the nuget using r8 doesn't seem to solve the issue. Same error occurs when trying to build the application that uses the Android nuget.

        <AndroidDexTool>d8</AndroidDexTool>
        <AndroidLinkTool>r8</AndroidLinkTool>
        <AndroidEnableDesugar>True</AndroidEnableDesugar>
        <AndroidEnableProguard>True</AndroidEnableProguard>
        <AndroidEnableMultiDex>True</AndroidEnableMultiDex>

• By the looks of it R8 is not inspiring confidence in microsoft just yet for them to make it the default option:

https://github.com/dotnet/android/blob/main/Documentation/guides/D8andR8.md#so-how-do-developers-use-it-what-are-sensible-msbuild-property-defaults

I will look further into this but in the meantime I take it that if you turn off R8 (as you already mentioned) and let the build system fallback to using 'proguard' or whatever then the resulting Android application runs acceptably right? Is there any problem in that regard?

[Pmr-precure]

We've run some tests based on your feedback:

• We run a sample MAUI app with the settings you indicated in the .csproj and we could replicate the error you're seeing.
• Rebuilding the nuget using r8 doesn't seem to solve the issue. Same error occurs when trying to build the application that uses the Android nuget.

        <AndroidDexTool>d8</AndroidDexTool>
        <AndroidLinkTool>r8</AndroidLinkTool>
        <AndroidEnableDesugar>True</AndroidEnableDesugar>
        <AndroidEnableProguard>True</AndroidEnableProguard>
        <AndroidEnableMultiDex>True</AndroidEnableMultiDex>

• By the looks of it R8 is not inspiring confidence in microsoft just yet for them to make it the default option:

https://github.com/dotnet/android/blob/main/Documentation/guides/D8andR8.md#so-how-do-developers-use-it-what-are-sensible-msbuild-property-defaults

I will look further into this but in the meantime I take it that if you turn off R8 (as you already mentioned) and let the build system fallback to using 'proguard' or whatever then the resulting Android application runs acceptably right? Is there any problem in that regard?

Hi,

I managed to build the project with R8 adding this to the proguard.cfg

-keep class com.laerdal.mcumgr.** { *; }
-keepattributes Annotation, Signature, EnclosingMethod, InnerClasses

[ksidirop-laerdal]

I guess you mean to say that this was added in the proguard.cfg of your application right? (or did you tweak the proguard.cfg of the Laerdal.McuMgr java-lib itself?)

-keep class com.laerdal.mcumgr.** { *; }
-keepattributes Annotation, Signature, EnclosingMethod, InnerClasses

Appreciate the follow up info.

[Pmr-precure]

I guess you mean to say that this was added in the proguard.cfg of your application right? (or did you tweak the proguard.cfg of the Laerdal.McuMgr java-lib itself?)

-keep class com.laerdal.mcumgr.** { *; }
-keepattributes Annotation, Signature, EnclosingMethod, InnerClasses

Appreciate the follow up info.

No no our application :)

[ksidirop-laerdal]

Quick headsup: I have this issue on my radar - just very busy during this period. But I will tackle this at some point for sure.

[Pmr-precure]

Quick headsup: I have this issue on my radar - just very busy during this period. But I will tackle this at some point for sure.

No problem:) as long we modify our proguard.cfg, everything is fine. :)

[Pmr-precure]

a little update to this. Using R8 and doing the erase method this is thrown:
java.lang.NoSuchMethodException: com.fasterxml.jackson.databind.SerializationFeature.values

An error occurred while erasing firmware: '[AFE.BE.020] Erasure failed 'com.fasterxml.jackson.databind.exc.InvalidDefinitionException: Cannot construct instance of io.runtime.mcumgr.response.img.McuMgrImageResponse (no Creators, like default constructor, exist): abstract types either need to be mapped to concrete types, have custom deserializer, or contain additional type information

** Update.
Adding to our proguard.cfg fixed the issue:
-keep class com.fasterxml.jackson.** { *; }
-keep class io.runtime.mcumgr.response.img.McuMgrImageResponse { *; }

[ksidirop-laerdal]

Noted and much appreciated.