Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bug]: Missing dSYM files from obfuscated and released iOS app #342

Open
1 task done
Tom3652 opened this issue Oct 8, 2024 · 3 comments
Open
1 task done

[bug]: Missing dSYM files from obfuscated and released iOS app #342

Tom3652 opened this issue Oct 8, 2024 · 3 comments
Labels
bug Something isn't working Needs Attention OP created or responded to issue and it needs attention. triage

Comments

@Tom3652
Copy link

Tom3652 commented Oct 8, 2024

Is there an existing issue for this?

  • I have searched the existing issues.

CLI Version

1.0.0

Firebase Tools version

13.20.2

Flutter Doctor Output

flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.24.3, on macOS 15.0.1 24A348 darwin-x64, locale fr-FR)
[✓] Android toolchain - develop for Android devices (Android SDK version 35.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 16.0)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2024.2)
[✓] VS Code (version 1.94.0)
[✓] Connected device (3 available)
[✓] Network resources

• No issues found!

Description

I am creating this issue to follow-up on this issue
After releasing an app with this command :

flutter build ipa --obfuscate --release --split-debug-info=/Users/foxtom/StudioProjects/MyProject/build --build-name=1.1.0 --build-number=1

And having this script as the last Build Phase in Xcode :

#!/bin/bash
PATH=${PATH}:$FLUTTER_ROOT/bin:$HOME/.pub-cache/bin
flutterfire upload-crashlytics-symbols --upload-symbols-script-path=$PODS_ROOT/FirebaseCrashlytics/upload-symbols --platform=ios --apple-project-path=${SRCROOT} --env-platform-name=${PLATFORM_NAME} --env-configuration=${CONFIGURATION} --env-project-dir=${PROJECT_DIR} --env-built-products-dir=${BUILT_PRODUCTS_DIR} --env-dwarf-dsym-folder-path=${DWARF_DSYM_FOLDER_PATH} --env-dwarf-dsym-file-name=${DWARF_DSYM_FILE_NAME} --env-infoplist-path=${INFOPLIST_PATH} --default-config=default
Capture d’écran 2024-10-08 à 09 47 48

The result is this crashlytics dashboard (please see Screenshots below)

Steps to reproduce

Try to create a .ipa file with an xcode archive using flutter build ipa --obfuscate --release --split-debug-info=/Users/foxtom/StudioProjects/MyProject/build --build-name=1.1.0 --build-number=1 for a complex project with a lot of dependencies (since i don't know which one is missing, or maybe some flutter dSYMs ?)

Expected behavior

I would like the flutterfire_cli to upload all the dSYMs for my project to crashlytics.

Screenshots

Capture d’écran 2024-10-08 à 09 41 06

Additional context and comments

Note : this may be an issue unrelated to flutterfire_cli and there are actually really missing dSYM files from the xcode archive that you can't find either, in that case it would be a Flutter issue when building a released obfuscated iOS IPA that doesn't put all the dSYM into the archive...

@Tom3652 Tom3652 added bug Something isn't working triage labels Oct 8, 2024
@Tom3652
Copy link
Author

Tom3652 commented Oct 8, 2024

I have just build in release mode without obfuscation and i saw 2 crashlytics missing dSYM very quickly by running into an error in my app.
One of the missing dSYM file was inside : /build/ios/Release-iphoneos/ and was the Runner.app.dSYM that didn't seem to be uploaded during the build.
The second missing dSYM file apparently doesn't exist on my local machine after the build.

I have found the first by running : mdfind -name .dSYM | while read -r line; do dwarfdump -u "$line"; done

It may be a first lead 🙏

@github-actions github-actions bot added the Needs Attention OP created or responded to issue and it needs attention. label Oct 8, 2024
@Tom3652
Copy link
Author

Tom3652 commented Oct 21, 2024

I am in an open case with Firebase support they are working on the issue and i will update here once i have more information.

@solshark
Copy link

Any news on this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Needs Attention OP created or responded to issue and it needs attention. triage
Projects
None yet
Development

No branches or pull requests

2 participants