[firebase_crashlytics]: Crashlytics build step crashes build of a macOS app - upload-symbols[44583:605681] Unable to get file attributes for dSYM file at path about flutterfire HOT 5 CLOSED

@tpkowastaken Can you open this issue again in https://github.com/invertase/flutterfire_cli

from flutterfire.

The fix is to simply Click the allow install builds only in xcode for the FlutterFire: "flutterfire upload-crashlytics-symbols" build step. Please add that to the flutterfire cli

edit: this only moves the problem to the release build state.

A temporary workaround is to use the legacy script:

"$PODS_ROOT/FirebaseCrashlytics/upload-symbols" --flutter-project "$PROJECT_DIR/firebase_app_id_file.json" 

and add input files:

"${DWARF_DSYM_FOLDER_PATH}/${DWARF_DSYM_FILE_NAME}"

"${DWARF_DSYM_FOLDER_PATH}/${DWARF_DSYM_FILE_NAME}/Contents/"

"${DWARF_DSYM_FOLDER_PATH}/${DWARF_DSYM_FILE_NAME}/Contents/Info.plist"

"$(TARGET_BUILD_DIR)/$(EXECUTABLE_PATH)"

"$(PROJECT_DIR)/firebase_app_id_file.json"

and check the For install build only

It should now look like this:

Now you need to create the firebase_app_id_file.json in the macos/firebase_app_id_file.json:

{
  "file_generated_by": "FlutterFire CLI",
  "purpose": "FirebaseAppID & ProjectID for this Firebase app in this directory",
  "GOOGLE_APP_ID": "[ios project id]",
  "FIREBASE_PROJECT_ID": "app-elevate-core",
  "GCM_SENDER_ID": "[GCM sender id]"
}

*You can find the values in [] in your GoogleService-Info.plist

PS: this is just a temporary workaround. Everytime you run flutterfire configure this gets reset. My way of keeping the changes is reverting macos/Runner.xcodeproj/project.pbxproj file back using git every time i run flutterfire configure.

Edit: I just tried it again and even this doesn't work. I still can't figure out why. I'm going to leave this to maintainers of flutterfire cli

from flutterfire.

@tpkowastaken Thank you for reporting this issue, and I'm glad that you found a solution for it. I've informed the team about updating the CLI docs to avoid any issues in the future.

from flutterfire.

@TarekkMA
Thank you for your answer I appreciate the quick response.
Hovewer shouldn't you forward it to the dev team instead? It shouldn't take too long to fix this. I believe it's just a simple edit of the Runner.xcworkspace that the flutterfire cli is already editing to put the bugged task in there already.
I wish you luck with resolving the issue internally and thank you for your effort.

from flutterfire.

My bad I haven't tested releasing the app yet. The script crashes even after that change when you try to release it. There is hovewer an issue already created - invertase/flutterfire_cli#314. I'm going to move the conversation there.

from flutterfire.