-
Notifications
You must be signed in to change notification settings - Fork 52
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]: Upload Crashlytics Symbols dSYM Files NOT working! #314
Comments
@russellwheatley any updates? |
I am also experiencing this. Have been since May 29th when I first integrated crashlytics -- have not had a successful dsym upload yet despite logs showing the script finishing successfully. |
Additionally, |
We're getting the same - I've tried spitting out the logs as described in #249 and they suggest the upload is successful:
But the dSYM(s) never appear in the Firebase console. If helpful, we're using Very Good CLI, so we have build flavours for production, staging and development, and a Firebase project per environment. This also means we don't have a permanent top-level |
@michaelowolf The console indicated that everything worked fine, and I received the output: However, when I checked Firebase Crashlytics, I found that the dSYM(s) were not uploaded. |
Exactly, @DougSig . |
Hey @Shatha-Naami - as mentioned here, please check to see if that file is missing. Could other folks experiencing this issue also let me know if that file is missing. Thanks 🙏 |
Hey @russellwheatley, I have a version of |
Hey @russellwheatley, |
@Shatha-Naami - what version of FlutterFire CLI are you using? The script is added to your build phases and it generates the file when you build you app (or uses existing file if you have built app previously). It is then used to upload symbols. |
@michaelowolf - you said you were using VGV CLI? They set their apps up to use build configuration. You should probably be configuring your app to use build configuration instead of target. In other words, use this flag - |
@russellwheatley After following this document and checking Xcode's Build Phases, I found that this run script was generated automatically and not created manually. |
Hi, I have been experiencing the same issue and that's just after freshly installing everything - new mac, new flutter, new xcode, new project. It's very easily reproducable, please look into it. Thank you for your time and effort. The issue in question: firebase/flutterfire#12990 |
There is a duplicate of this already: |
@tpkowastaken I follow your steps, and this is the final result: and I'm already update values on So what I miss in the steps? |
@Shatha-Naami |
I encountered the same issue. After investigating the source code:(
I noticed that there are three options In order to make multi flavor setups working you need to change the firebase.json to uses {
"flutter": {
"platforms": {
"ios": {
"default": {
"projectId": "your-project-id",
"appId": "1:1:ios:1",
"uploadDebugSymbols": false,
"fileOutput": "ios/Runner/GoogleService-Info.plist"
}
},
"dart": {
"lib/firebase_options.dart": {
"projectId": "your-project-id",
"configurations": {
"ios": "1:1:ios:1"
}
}
}
}
}
}
to {
"flutter": {
"platforms": {
"ios": {
"targets": {
"develop": {
"projectId": "your-project-id-develop",
"appId": "1:1:ios:1",
"uploadDebugSymbols": true,
"fileOutput": "ios/Runner/GoogleService-Info.plist"
},
"production": {
"projectId": "your-project-id",
"appId": "1:1:ios:1",
"uploadDebugSymbols": true,
"fileOutput": "ios/Runner/GoogleService-Info.plist"
}
}
},
"dart": {
"lib/firebase_options.develop.dart": {
"projectId": "your-project-id-develop",
"configurations": {
"ios": "1:1:ios:1"
}
},
"lib/firebase_options.production.dart": {
"projectId": "your-project-id",
"configurations": {
"ios": "1:1:ios:1"
}
}
}
}
}
} Furthermore in the All those changes should result in a Hope this helps. |
@RaphaelJenni |
@Shatha-Naami Update the firebase dependencies to the newest version and run |
@RaphaelJenni Thanks All! |
Confirmed that this helped, without need to change any Firebase package version or even cleaning project again. |
@russellwheatley sorry to necro this - just wanted to mention that (having finally had time to come back to this) your suggestion worked. Thanks for the help with that, I'd missed completely the multi-build configuration set up section in the README. Probably not the right place to mention this (and I may be missing more docs elsewhere!), but since https://firebase.flutter.dev/docs/overview/ is marked out of date and points to https://firebase.google.com/docs/flutter/setup, it would be really good to get some of the Flutterfire CLI readme included in or linked to from those Firebase docs. |
@RaphaelJenni I am using flavors in my project and I tried to use your solution:
I tried to use your way because I am also using flavors. After doing the changes I am unable to run my project. Throws error: Can you please share the User defined flavor setup screenshot? and FlutterFire script needs to run at last in build phase? |
Is there an existing issue for this?
CLI Version
1.0.0
Firebase Tools version
13.11.2
Flutter Doctor Output
Description
I followed the Firebase Crashlytics setup guide for Flutter to integrate Firebase Crashlytics into my Flutter app. While I am able to see crash reports and user metrics in the Firebase Analytics dashboard, the dSYM files are not being uploaded automatically.
Steps to reproduce
Expected behavior
The dSYM files should be uploaded automatically without any manual intervention.
Actual Behavior:
Although crash reports and user metrics appear in the Firebase Analytics dashboard, the dSYM files are not uploaded automatically.
Screenshots
Additional context and comments
Flutter version: 3.22.2
Firebase Crashlytics version: ^4.0.1
Xcode version: 15.4
The text was updated successfully, but these errors were encountered: