upload-symbols: Path to CoreSymbolication is invalid

[otaviolima]

Description

Hello,

My team is facing the same issue as discussed in #14158, where dsyms are not uploaded because the upload-symbols binary complains that the CoreSymbolication path is not valid.

The other issue was resolved after the CI machines were updated to newer MacOS. However, we are already using a MacOS version that is supported by Xcode 16.2

The issue started happening once we migrated our CI fleet to Xcode 16.2 and MacOS 15.1.1. To debug and investigate the issue, we tried several different versions of upload-symbols, and all of them failed with similar issues.

The paths to CoreSymbolication seem correct in the machine and should be accessible to the user that the CI uses.

Reproducing the issue

The issue can only be reproduced in our CI machines. In our local development, we were unable to reproduce the issue in any combination of MacOS version and Xcode version, and upload-symbols version (Downloaded from git history in this repo).

Our minimal way to reproduce the issue consists of creating a very small dsym.zip and run it against different versions of the upload-symbols as the bash script below

APP_ID="redacted"
# Note, to reduce the log size we created a very small zip with only one dSYM file inside
# Uploaded to this issue as convenience, but anything fails. 
DSYM_PATH="./dsym.zip"

BINARIES=(
    upload-symbols
    # Can add here any other binary for debugging
)

for binary in "${BINARIES[@]}"; do
    echo "------------------------------------"
    echo "Uploading dSYM for ${binary}"
    ./${binary} -d -ai "${APP_ID}" -p ios "${DSYM_PATH}"
    echo "Done uploading dSYM for ${binary}"
    echo "------------------------------------"
done

dsym.zip

Firebase SDK Version

11.5.0

Xcode Version

16.2

Installation Method

CocoaPods

Firebase Product(s)

Crashlytics

Targeted Platforms

iOS

Relevant Log Output

% bash upload.sh
------------------------------------
Uploading dSYM for upload-symbols
upload-symbols 3.20 build 39

Arguments:
Debug mode enabled
Google App ID: <redacted>
Platform: ios
# Note, to reduce the log size we created a very small zip with only one dSYM file inside
DSYM Paths: ["./dsym.zip"]

Inspecting next path: ./dsym.zip
Found archive at path: ./dsym.zip
Inspecting next path: /var/folders/sb/t8_fztcj0p1g2qnvn528lpb80000gn/T//./dsym.zip.unzipped/FBSDKCoreKit_Basics.framework.dSYM
Found dSYM at path: /var/folders/sb/t8_fztcj0p1g2qnvn528lpb80000gn/T//./dsym.zip.unzipped/FBSDKCoreKit_Basics.framework.dSYM
Begin processing dSYM at /var/folders/sb/t8_fztcj0p1g2qnvn528lpb80000gn/T/dsym.zip.unzipped/FBSDKCoreKit_Basics.framework.dSYM/Contents/Resources/DWARF/FBSDKCoreKit_Basics
2025-02-05 05:41:29.414 upload-symbols[74881:4740476] Path to CoreSymbolication is invalid, aborting
upload.sh: line 9: 74881 Segmentation fault: 11  ./${binary} -d -ai "${APP_ID}" -p ios "${DSYM_PATH}"
Done uploading dSYM for upload-symbols

If using Swift Package Manager, the project's Package.resolved

Expand Package.resolved snippet

Replace this line with the contents of your Package.resolved.

If using CocoaPods, the project's Podfile.lock

Expand Podfile.lock snippet

Replace this line with the contents of your Podfile.lock!

[google-oss-bot]

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.