Android - Google Play Store: Recover the original stack trace

[GitToTheHub]

Hi,

when I want to release an App on Google Play I get two warnings (translated from german to english):

Warning
There is no disclosure file associated with this app bundle. If you are using obfuscated code (R8/ProGuard), uploading a disclosure file makes it easier to analyze and troubleshoot crashes and ANRs. The app size can be reduced with the help of R8/ProGuard. Further information

Warning
This app bundle contains native code and you have not uploaded any symbols for debugging. We recommend that you upload an icon file so that your crashes and ANRs can be better analyzed and debugged. Further information

I saw, that normally a mapping file is shipped with an app bundle. I switched from APK to AAB during the app lifecycle on Google Play, is this maybe the problem that the mapping file is not there? Because it means:

Warning: If you're shipping APKs, the mapping.txt file isn't automatically bundled with your APK. Android Studio saves the mapping file in the /build/outputs/mapping/ directory. The mapping file is overwritten every time you build your project, so you must save a copy each time you publish a new release.

See: https://developer.android.com/topic/performance/app-optimization/test-and-troubleshoot-the-optimization#recover-original-stack-trace

It says also, that the mapping file is found in /build/outputs/mapping/ but I don't see a mapping directory in /build/outputs. Or can I ignore the warning and it's wrong?

Regards,

Manuel

[breautek]

It says also, that the mapping file is found in /build/outputs/mapping/ but I don't see a mapping directory in /build/outputs. Or can I ignore the warning and it's wrong?

Google always warns if you don't provide a mapping. But the mapping is only generated if your build actually uses Proguard, which cordova builds does not.

Because Cordova usually refers to functions by string, using reflection for the cordova bridge, enabling Proguard breaks the cordova framework since proguard will obsfucate/minimize function names to create a smaller build. The mapping is so it can take the proguard output and translate it back to the original symbols.

Because Cordova build doesn't use proguard though, any errors originating from cordova framework or the cordova project should already show the original symbols in any errors captured and reported through Google Play. So the warning can be ignored imo.

[GitToTheHub]

Thank you, I see it's written ... If you are using obfuscated code. I thought the warning was coming, because it's obfuscated. I've thought, Google only shows me relevant warnings. Maybe this could be documented somewhere, so other developers know it's only an empty warning. Your answer is very good and explains it.