De-obfuscating flutter stack traces in firebase crashlytics

[eukevin]

We are attempting to build android and iOS flutter apps with code obfuscation via yaml file:

flutter build appbundle --release --obfuscate --split-debug-info=build/app/outputs/symbols

flutter build ipa --export-options-plist ~/export_options.plist --obfuscate --split-debug-info=build/app/outputs/symbols

and publishing to Firebase. Unfortunately our stack traces in crashlytics remain obfuscated. The following has been added to build.gradle:

            firebaseCrashlytics {
                mappingFileUploadEnabled true
            }

and the following script has been added to codemagic.yaml to explicitly upload dSYM files to iOS (although I suspect this is unrelated):

          echo "Find build artifacts"
          dsymPath=$(find $CM_BUILD_DIR/build/ios/archive/Runner.xcarchive -name "*.dSYM" | head -1)
          if [[ -z ${dsymPath} ]]
          then
            echo "No debug symbols were found, skip publishing to Firebase Crashlytics"
          else
            echo "Publishing debug symbols from $dsymPath to Firebase Crashlytics"
            ls -d -- ios/Pods/*
            $CM_BUILD_DIR/ios/Pods/FirebaseCrashlytics/upload-symbols \
              -gsp ios/Runner/GoogleService-Info.plist -p ios $dsymPath
          fi

Is there some configuration piece missing? The documentation seems to suggest that the de-obfuscation should happen automatically.

[himesh-cm]

Hi @eukevin, Let me have a look, I will get back to you.

[himesh-cm]

@eukevin, Can you please share the build id as well?
The path to the symbols file is different i believe in your build command and the upload script

[eukevin]

Thanks for looking! The most recent build showing this issue was 63bec59cdb18b00fe5a49e0f

[eukevin]

Btw at least on the iOS side the symbol upload looked successful.

[himesh-cm]

Hi @eukevin , Apologies for the delayed reply. Obfuscated symbols files for android are located in the output_directory directory in the app.android-arm64.symbols file or similarly named based on your build architecture.

[dtrdic]

This discussion is being closed due to no activity in the last 14 days. You can reopen the discussion at any time if needed.

[jonmountjoy]

@eukevin did you resolve this? Do you really have to do upload the dSYM via your own script, and what did you need to do with Android? Thank you. There are no docs on this - and if I get it working, I'll try and contribute some.

Also, when installing Crashlytics it also installs a build phase for Xcode to upload symbols - wouldn't that run, even if on CodeMagic?