Can we access your project?
Current Behavior
Firebase Crashlytics is enabled in my FlutterFlow project.
All iOS builds and App Store deployments are performed through FlutterFlow. Crashlytics is receiving crash events, but the Firebase Crashlytics dSYMs page reports "Missing (required)" dSYM files for multiple iOS app versions/builds.
Expected Behavior
When Crashlytics is enabled in FlutterFlow and an iOS app is built/deployed through FlutterFlow, the required dSYM files should be generated and uploaded to Firebase Crashlytics automatically.
Firebase should be able to symbolicate iOS crash reports without showing "Missing dSYM (required)" warnings.
I should not need to manually locate and upload dSYM files after every FlutterFlow iOS deployment.
Steps to Reproduce
- Open a FlutterFlow project connected to Firebase.
- Go to Settings & Integrations > Project Setup > Firebase.
- Enable Firebase Crashlytics.
- Build and deploy the iOS app through FlutterFlow.
- Use the deployed iOS app so Crashlytics receives crash events.
- Open Firebase Console > Crashlytics > dSYMs.
- Observe that dSYM files for the deployed iOS build are listed as "Missing (required)".
- Repeat with subsequent FlutterFlow iOS builds and observe that additional builds also report missing dSYMs.
Reproducible from Blank
Bug Report Code (Required)
IT4kj8nc24lgrsdc187pbfpavCo7C2Y5TL03pu0bFEggGLbrBIYMacjOTFVCZ72qdEFXKEWLsGQE/+DwkvDEUfQDNQSuG5hz+s1iWzvxWTq/aoSMCpOVP0RTM9xmGkiw07uzohElANhvV3wB7DqXe+u+ShDqNKH6Zwh9f6PHaOI=
Visual documentation
Firebase Crashlytics reporting multiple “Missing (required)” dSYM files across several iOS app versions/builds.
The Runner → Build Phases section of the iOS project generated by FlutterFlow. The visible Run Script is only the standard Flutter xcode_backend.sh build script, and no separate Crashlytics symbol upload phase is visible.
The project is built and deployed to iOS entirely through FlutterFlow, with Crashlytics enabled in FlutterFlow settings.
Environment
- FlutterFlow version: 3.38.6
- Platform: Desktop on macOS
- Browser name and version: N/A (FlutterFlow Desktop)
- Operating system and version affected: macOS Tahoe 26.5.2
Additional Information
This affects my ability to properly diagnose iOS crashes in production.
I rely on FlutterFlow for the complete iOS build and deployment process, so manually locating and uploading dSYM files after every release is not a practical workaround.
The issue has already occurred across multiple app versions/builds, so it appears to be recurring rather than isolated to a single build.
My goal is to have Crashlytics work as expected when enabled in FlutterFlow, with the required dSYM files automatically uploaded during the iOS build/deployment process.
Can we access your project?
Current Behavior
Firebase Crashlytics is enabled in my FlutterFlow project.
All iOS builds and App Store deployments are performed through FlutterFlow. Crashlytics is receiving crash events, but the Firebase Crashlytics dSYMs page reports "Missing (required)" dSYM files for multiple iOS app versions/builds.
Expected Behavior
When Crashlytics is enabled in FlutterFlow and an iOS app is built/deployed through FlutterFlow, the required dSYM files should be generated and uploaded to Firebase Crashlytics automatically.
Firebase should be able to symbolicate iOS crash reports without showing "Missing dSYM (required)" warnings.
I should not need to manually locate and upload dSYM files after every FlutterFlow iOS deployment.
Steps to Reproduce
Reproducible from Blank
Bug Report Code (Required)
IT4kj8nc24lgrsdc187pbfpavCo7C2Y5TL03pu0bFEggGLbrBIYMacjOTFVCZ72qdEFXKEWLsGQE/+DwkvDEUfQDNQSuG5hz+s1iWzvxWTq/aoSMCpOVP0RTM9xmGkiw07uzohElANhvV3wB7DqXe+u+ShDqNKH6Zwh9f6PHaOI=
Visual documentation
Firebase Crashlytics reporting multiple “Missing (required)” dSYM files across several iOS app versions/builds.
The Runner → Build Phases section of the iOS project generated by FlutterFlow. The visible Run Script is only the standard Flutter xcode_backend.sh build script, and no separate Crashlytics symbol upload phase is visible.
The project is built and deployed to iOS entirely through FlutterFlow, with Crashlytics enabled in FlutterFlow settings.
Environment
Additional Information
This affects my ability to properly diagnose iOS crashes in production.
I rely on FlutterFlow for the complete iOS build and deployment process, so manually locating and uploading dSYM files after every release is not a practical workaround.
The issue has already occurred across multiple app versions/builds, so it appears to be recurring rather than isolated to a single build.
My goal is to have Crashlytics work as expected when enabled in FlutterFlow, with the required dSYM files automatically uploaded during the iOS build/deployment process.