Xamarin-android: Debug symbols upload on Google Play Console for better crash information

[EmilAlipiev]

When we upload an app bundle or apk, below warning is returned from google play console. Question is what kind of source symbols should we or can we upload here? I am guessing that it is it not pdb files :) Is there a way for Xamarin.forms applications for android to get symbols and better crash information?

This App Bundle contains native code, and you've not uploaded debug symbols. We recommend that you upload a symbol file to make your crashes and ANRs easier to analyse and debug.

[jonathanpeppers]

This was solved for obfuscated Java/Kotlin code here:

https://github.com/xamarin/xamarin-android/pull/5304

It doesn't look like we have solved this for native code, which would include AOT'd .NET assemblies.

[tbrentlong]

I'm seeing the same issue when uploading a bundle build via VS2019. Is there a file somewhere that can be uploaded? I also still get the deobfuscation message noted in 5186 even though I'm not using a code shrinker.

[jonathanpeppers]

@tbrentlong as mentioned in #5304, I think you would need to use AndroidLinkMode=r8 to get the mapping.txt file.

Can you share a screenshot of the warning you get?

[Eversor]

I'm getting the same issue here, i cannot find the mapping.txt in the bin/Release folder, and i don't know where to change the cfg file either.

Microsoft Visual Studio Community 2019
Version 16.7.6
VisualStudio.16.Release/16.7.6+30611.23
Microsoft .NET Framework
Version 4.8.04084

Xamarin 16.7.000.456 (d16-7-6@f8d55b6)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.

Xamarin.Android SDK 11.0.2.0 (d16-7/025fde9)
Xamarin.Android Reference Assemblies and MSBuild support.
Mono: 83105ba
Java.Interop: xamarin/java.interop/d16-7@1f3388a
ProGuard: Guardsquare/proguard/proguard6.2.2@ebe9000
SQLite: xamarin/sqlite/3.32.1@1a3276b
Xamarin.Android Tools: xamarin/xamarin-android-tools/d16-7@017078f

[dellis1972]

VS 2019 16.7.x does not include the fix from #5304 since it was released before the fix was merged.
You will need to be on 16.9.x.
Also PR #5318 made it an "opt-in" feature. Which means you need to set the following in
your release config in the csproj in order to activate it.

<AndroidProguardMappingFile>$(OutputPath)mapping.txt</AndroidProguardMappingFile>

[Eversor]

Thank you for the information, will try to update and post my findings... Do i need to activate Proguard code shrinking for the mappings to be outputted?

[dellis1972]

The AndroidProguardMappingFile only works with r8 / d8. It should output the mapping if those are set.

[plaili]

It doesn't look like we have solved this for native code, which would include AOT'd .NET assemblies.

Is this issue with no debug symbols for native code tracked anywhere? Or will it be tracked here?