Search code examples
iosxcodefirebasecrashlyticsfirebase-crash-reporting

Could not complete submission of dSYM, File no longer exists at (null)

I have migrated Fabric to Firebase/Crashlytics and I am getting this below build error for my run script in an iOS project,

Build Phase - Run Script

# Name of the resource we're selectively copying
GOOGLESERVICE_INFO_LOCATION=${PROJECT_DIR}/${TARGET_NAME}/App/Scripts/GoogleService-Info.plist

# Upload sysmbol
echo "Uploading dsym file"

"${PODS_ROOT}/FirebaseCrashlytics/upload-symbols" -gsp ${GOOGLESERVICE_INFO_LOCATION} -p ios ${DWARF_DSYM_FOLDER_PATH}/${DWARF_DSYM_FILE_NAME}

Build Error

[31merror: Could not complete submission of dSYM at /Users/me/Library/Developer/Xcode/DerivedData/Project-cmkidnrcwbunsqezgsrutqkmnivn/Build/Intermediates.noindex/ArchiveIntermediates/Project/BuildProductsPath/ReleaseOfficial-iphoneos/Project.app.dSYM: Error Domain=com.crashlytics.mac.error-domain.process-dsym Code=2 "File no longer exists at (null)" UserInfo={NSLocalizedFailureReason=File no longer exists at (null)}

Suggested in solution didn't work for me.

How to resolve it?

Solution

  • I recently got a new Mac and faced the same issue.

    After trying lot of different things with no success, I found what was wrong. All I had to do, is to move my upload DSYM script at the bottom of the build phases script list.

    We talk about this script:

    "${PODS_ROOT}/FirebaseCrashlytics/upload-symbols" -gsp "${PROJECT_DIR}/YourPathToYourGoogleServiceFile/GoogleService-Info.plist" -p ios "${DWARF_DSYM_FOLDER_PATH}/${DWARF_DSYM_FILE_NAME}"

    It has to be the last one executed

    If this does not work, try this :

    1. Comment your DSYM script, then archive your app.
    2. Your archive should complete with success
    3. Uncomment your DSYM script, and place it to the bottom list. (see correct order below)
    4. Build a new archive.

    Correct order :

    1. run firebaseCrashlytics script.
    2. run [CP] Embed pods frameworks
    3. run DSYM Script

    NB: In some cases, having a path containing some white spaces such as 'Supporting files' may lead to unexpected behaviour.