[Xcode, Sentry CLI] Upload fails in background

[trooperandz]

OS:

• [ ] Windows
• [x] MacOS (14.5)
• [ ] Linux

Platform:

• [x] iOS
• [ ] Android

SDK:

• [x] @sentry/react-native (>= 1.0.0)
• [ ] react-native-sentry (<= 0.43.2)

SDK version: 5.31.1

react-native version: 0.73.7

Are you using Expo?

• [ ] Yes
• [x] No

Are you using sentry.io or on-premise?

• [x] sentry.io (SaaS)
• [ ] on-premise

If you are using sentry.io, please post a link to your issue so we can take a look: (I do not have a link that I know of)

Configuration:

(@sentry/react-native)

Sentry.init({
  dsn: 'https://...sentry.io...'
});

---

I have the following issue:

When attempting to upload source maps and debug symbols for iOS during the release build process, the Sentry uploads only work when the foreground flag is enabled: export SENTRY_CLI_EXTRA_ARGS="--force-foreground". If the foreground flag is not set, we see in the MacOS crash logs that the sentry-cli is crashing during execution. This is with the sentry-cli version 2.34.0.

Steps to reproduce:

• Step 1 After running the sentry wizard to enable source map uploads (npx @sentry/wizard@latest -i reactNative), ensure that the following content in the "Bundle React Native code and images" build phase is as follows:

set -e

WITH_ENVIRONMENT="../node_modules/react-native/scripts/xcode/with-environment.sh"
REACT_NATIVE_XCODE="../node_modules/react-native/scripts/react-native-xcode.sh"
SENTRY_XCODE="../node_modules/@sentry/react-native/scripts/sentry-xcode.sh"
BUNDLE_REACT_NATIVE="/bin/sh $SENTRY_XCODE $REACT_NATIVE_XCODE"
/bin/sh -c "$WITH_ENVIRONMENT \"$BUNDLE_REACT_NATIVE\""

Additionally, ensure that the "Upload Debug Symbols to Sentry" build phase has the following content:

/bin/sh ../node_modules/@sentry/react-native/scripts/sentry-xcode-debug-files.sh

• Step 2 Run a Release build in Xcode until successful completion, and observe that during the build process, system notifications appear for both build phases:

• Step 3 Observe that system notifications never show for the Sentry completion, and that no source map release artifact or debug files have been uploaded to your Sentry project dashboard. Also observe that in the MacOS Console.app crash logs, there are two crash reports for the sentry-cli:

• Step 4 Add the following to your .xcode.env file: export SENTRY_CLI_EXTRA_ARGS="--force-foreground" and run another Release build in Xcode.

• Step 5 Observe that the Sentry source map uploads were successful, and that debug files and a release artifact appears in your project dashboard.

Actual result: Before adding the export SENTRY_CLI_EXTRA_ARGS="--force-foreground" environment variable, no debug files or source map uploads occur.

Expected result: Source map uploads should occur regardless of the --force-foreground flag.

Supporting logs and crash report details (see attachments)

sentry-logs-from-failed-upload.txt sentry-cli-crash1.txt sentry-cli-crash2.txt

[Krupskis]

Seems to be the same issue as getsentry/sentry-react-native#4063

[trooperandz]

Seems to be the same issue as #4063

@Krupskis I don't think that this is the same issue. Our issue was not with the main.jsbundle; it was when the bundle upload step was occurring. Our main.jsbundle file was created successfully during the process.

[krystofwoldrich]

Hi @trooperandz, thank you for the super detailed steps,

when uploading from background the process output is redirected to a file.

You can find the file path in the output before redirection.

output: sentry-cli - Continuing in background.
output: sentry-cli - Output is redirected to /var/folders/2k/q6nq8shs0zz25v_lsc39zjg80000gn/T/25201362-2391-40db-b6f8-f530012def6e

Can you try the upload once more and share the content of the file?

[trooperandz]

Thank you @krystofwoldrich . Here is the output file which you requested:

background-output-log.txt

[krystofwoldrich]

Thank you for the log, it seems to be the same error as

• https://github.com/getsentry/sentry-cli/issues/1895

Likely caused by bump of the CLI dependency curl-sys to 0.4.73+curl-8.8.0 in https://github.com/getsentry/sentry-cli/pull/2096/files#diff-13ee4b2252c9e516a0547f2891aa2105c3ca71c6d7a1e682c69be97998dfc87eR615.

[krystofwoldrich]

Affected CLI versions https://github.com/getsentry/sentry-cli/releases/tag/2.32.2 to current

[krystofwoldrich]

@loewenheim @szokeasaurusrex Can we lock in the older version of curl-sys till a fix from the lib side or our side is provided for the latest versions?

To avoid Sentry CLI regressions by accidental upgrades in the future.

[szokeasaurusrex]

@krystofwoldrich, yeah, I think this should be possible

[szokeasaurusrex]

The fix will be available in 2.36.1, which we will release shortly

[szokeasaurusrex]

Reopening this issue. I was able to reproduce this issue even after downgrading curl-sys, indicating that downgrading likely did not fix the issue. Furthermore, the downgrade caused #2155, so now I plan to re-upgrade curl-sys.

We will continue investigating how to fix this issue. For now, we recommend running Sentry CLI with --force-foreground when uploading React Native debug files.