no deobfuscation file associated with this App Bundle [EAS BUILD]

Summary

When submit to google play


Warning
There is no deobfuscation file associated with this App Bundle. If you use obfuscated code (R8/proguard), uploading a deobfuscation file will make crashes and ANRs easier to analyse and debug. Using R8/proguard can help reduce app size. Learn more

Warning
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. Learn more

Managed or bare workflow? If you have `ios/` or `android/` directories in your project, the answer is bare!

managed

What platform(s) does this occur on?

Android

SDK Version (managed workflow only)

Environment

Reproducible demo

Build with eas build.
Upload the bundle to play store .

Issue Analytics

State:
Created 2 years ago
Reactions:5
Comments:8 (1 by maintainers)

Top GitHub Comments

12reactions

brentvatnecommented, Jan 4, 2022

you can enable debug symbols if you want: https://stackoverflow.com/questions/63373245/how-to-add-debug-symbols-to-build-gradle. use a config plugin to modify build.gradle accordingly.

we may enable this by default in the future. we do not currently.

4reactions

andreasciamannacommented, Oct 3, 2022

So, it seems to be working fine.

While preparing the new release, I got no warnings about deobfuscation on the Play Store.

Probably it’s unrelated, but it is worth mentioning that we faced some issues with the app crashing on Android, after publishing, and as soon as the app started. This led to some additional changes in the Proguard configuration:

"plugins": [
  [
    "expo-build-properties",
    {
      "android": {
        "enableProguardInReleaseBuilds": true,
        "extraProguardRules": "-keep public class com.horcrux.svg.** {*;}",
        "allowBackup": false
      }
    }
  ]
],