Bump @sentry/react-native from 8.15.1 to 8.24.0

[dependabot]

Bumps @sentry/react-native from 8.15.1 to 8.24.0.

Release notes

Sourced from @​sentry/react-native's releases.

8.24.0

Features

• Add enableNdkAppHangTracking and ndkAppHangTimeoutIntervalMillis options to enable Android NDK app hang tracking (#6548)

Fixes

• Warn when replay sample rates are set but the Replay integration is missing (#6612)
• Fix time to display spans causing transactions to be dropped by Relay (#6608)
• Fix Expo iOS build failing when the project path contains spaces (#6604)
• Fix Android fragment memory leak in RNSentryReactFragmentLifecycleTracer (#6599)
• Ship a named navigation transaction when re-navigating to the focused route with new params, instead of an unnamed "Route Change" (#6606)

Dependencies

• Bump Android SDK from v8.52.0 to v8.53.0 (#6586)
  • changelog
  • diff
• Bump JavaScript SDK from v10.69.0 to v10.71.0 (#6580, #6610)
  • changelog
  • diff

8.23.0

Changes

• Migrate iOS internals from the deprecated PrivateSentrySDKOnly SPI to SentrySDK.internal (#6541)

  Re-lands #6380, reverted in 8.20.0 by #6491 because it broke iOS screenshot capture. The underlying sentry-cocoa bug is fixed in 9.24.0.

[!WARNING] Action required if you target React Native < 0.75. RNSentry now ships Swift code, which makes it a Swift pod under CocoaPods. If your Podfile doesn't already modularize React Native's ObjC pods (RN >= 0.75 does this by default), add use_modular_headers! to your ios/Podfile before running pod install. Otherwise pod install fails with an error like: The Swift pod 'RNSentry' depends upon 'React-hermes', which does not define modules.

Fixes

• Send SDK-internal diagnostics to the debug logger instead of the Sentry Logs API (#6585)

  Ten internal warnings in the TurboModule instrumentation, scope sync and the Expo Router error boundary were written against logger, which captures a log record and sends it to your project. They now go to debug, printed only when the SDK is initialized with debug: true.

• Measure callback-style native module calls until their completion callback fires (#6561)

  Bridge methods that report completion through success/failure callbacks instead of a Promise return undefined, so they were recorded as sync calls with a near-zero duration. Their turbo_module.* durations are now correct, and slow ones produce a native.turbo_module breadcrumb. On the Old Architecture a failure callback is also counted as an error, following React Native's own (failure, success) trailing-argument convention.

• Resolve config-plugins through the expo package in the Expo config plugin (#6581)

• Make the RNSentry SPEC CHECKSUM in Podfile.lock machine-independent (#6534)

... (truncated)

Changelog

Sourced from @​sentry/react-native's changelog.

8.24.0

Features

• Add enableNdkAppHangTracking and ndkAppHangTimeoutIntervalMillis options to enable Android NDK app hang tracking (#6548)

Fixes

• Warn when replay sample rates are set but the Replay integration is missing (#6612)
• Fix time to display spans causing transactions to be dropped by Relay (#6608)
• Fix Expo iOS build failing when the project path contains spaces (#6604)
• Fix Android fragment memory leak in RNSentryReactFragmentLifecycleTracer (#6599)
• Ship a named navigation transaction when re-navigating to the focused route with new params, instead of an unnamed "Route Change" (#6606)

Dependencies

• Bump Android SDK from v8.52.0 to v8.53.0 (#6586)
  • changelog
  • diff
• Bump JavaScript SDK from v10.69.0 to v10.71.0 (#6580, #6610)
  • changelog
  • diff

8.23.0

Changes

• Migrate iOS internals from the deprecated PrivateSentrySDKOnly SPI to SentrySDK.internal (#6541)

  Re-lands #6380, reverted in 8.20.0 by #6491 because it broke iOS screenshot capture. The underlying sentry-cocoa bug is fixed in 9.24.0.

[!WARNING] Action required if you target React Native < 0.75. RNSentry now ships Swift code, which makes it a Swift pod under CocoaPods. If your Podfile doesn't already modularize React Native's ObjC pods (RN >= 0.75 does this by default), add use_modular_headers! to your ios/Podfile before running pod install. Otherwise pod install fails with an error like: The Swift pod 'RNSentry' depends upon 'React-hermes', which does not define modules.

Fixes

• Send SDK-internal diagnostics to the debug logger instead of the Sentry Logs API (#6585)

  Ten internal warnings in the TurboModule instrumentation, scope sync and the Expo Router error boundary were written against logger, which captures a log record and sends it to your project. They now go to debug, printed only when the SDK is initialized with debug: true.

• Measure callback-style native module calls until their completion callback fires (#6561)

  Bridge methods that report completion through success/failure callbacks instead of a Promise return undefined, so they were recorded as sync calls with a near-zero duration. Their turbo_module.* durations are now correct, and slow ones produce a native.turbo_module breadcrumb. On the Old Architecture a failure callback is also counted as an error, following React Native's own (failure, success) trailing-argument convention.

• Resolve config-plugins through the expo package in the Expo config plugin (#6581)

... (truncated)

Commits

• 87bdc65 release: 8.24.0
• 7f88878 fix(ios): Stay on Cocoa SDK 9.24.0 (revert 9.26.0 bump) (#6622)
• f65535b chore: update scripts/update-maestro.sh to v2.9.0 (#6620)
• 8e3cabb fix(replay): Warn when replay sample rates are set but the Replay integration...
• f0619dc fix(tracing): Name transaction when re-navigating to focused route with new p...
• 2e64504 fix(tracing): keep time to display spans within transaction bounds (#6608)
• f6ce4ff chore: update scripts/update-javascript.sh to 10.71.0 (#6610)
• f8d1a37 chore: update scripts/update-wizard.sh to v7.0.3 (#6611)
• fd963e7 fix(ios): Quote script paths so Expo iOS build works with spaces in the proje...
• d6784d9 fix(deps): Bump deepmerge-ts to ^8.0.0 to resolve stack-exhaustion advisory (...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)