chore(deps): update Cocoa SDK to v9.30.0

[github-actions]

Bumps scripts/update-cocoa.sh from 9.28.0 to 9.30.0.

Auto-generated by a dependency updater.

Changelog

9.30.0

Features

• Update option stability without changing defaults (#9134, #9175):
  • enableUnhandledCPPExceptionsV2 remains non-deprecated under options.experimental in v9, disabled by default, with dictionary-based initialization support.
  • enablePersistingTracesWhenCrashing is now stable and remains disabled by default.
  • attachViewHierarchy is now stable and remains disabled by default.
  • enableTimeToFullDisplayTracing is now stable and remains disabled by default because applications must explicitly call SentrySDK.reportFullyDisplayed().
  • swiftAsyncStacktraces is now stable and remains disabled by default.
  • enableGraphQLOperationTracking is now stable and remains disabled by default.
  • enableFileManagerSwizzling is now stable, remains disabled by default, and supports dictionary-based initialization.
• Add connection_type to the device context of events, which reports wifi, ethernet, cellular, or none (#9097).
  On iOS, cellular connections additionally report the network technology in connection_effective_type, for example 4g or 5g.

Fixes

• Keep standalone objc extensions in static builds by adding referenced dummy NSObject subclasses, and lint for this with a SwiftSyntax SwiftLint extra rule (#9160)
• Send envelopes captured during a connectivity-triggered cache drain without waiting for another trigger (#9171)
• Preserve full resolution when masking feedback, error, and crash screenshots, including screenshots captured through the React Native bridge, without changing Session Replay resolution or redactions (#9179)
• Compact raw MetricKit diagnostic attachments to reduce their upload size and attachment quota usage (#9183)

9.29.2

Fixes

• Stop sending scope attachments with crashes and other fatal events captured from a previous app run, because those attachments belong to the current run. Use beforeSendWithHint to attach files to fatal events (#9153)
• Prevent an isMetricKitEvent unrecognized selector crash when statically linking the SDK without -ObjC, including when MetricKit is disabled (#9155)

9.29.1

Caution

Known issue: This release can crash apps statically linking the SDK without -ObjC with -[SentryEvent isMetricKitEvent]: unrecognized selector, even when MetricKit is disabled. Add -ObjC to the app target's linker flags, preserving $(inherited), or pin to 9.29.0 until a fix is released. See #9154.

Fixes

• Add experimental support for the new URLSession HTTP loader for automatic network instrumentation, preserving original request details in Session Replay after redirects. Opt in with options.experimental.enableNewURLLoaderSwizzling = true (disabled by default) (#8845)
• Preserve MetricKit diagnostics containing frames without a binary UUID instead of dropping the entire diagnostic (#9080)
• Session Replay: Populate trace_ids in replay events to enable searching replays by trace ID (#9092)
• Retain raw MetricKit diagnostic attachments when call-stack decoding fails and enableMetricKitRawPayload is enabled, without attaching unrelated current-thread stack traces (#9070)
• Prevent duplicate HTTP spans and breadcrumbs when watchOS resumes an internal URLSession task copy after the original request finishes (#9095)
• Remove the compiler deprecation warning for enableAppHangTracking so applications can continue opting out of App Hang tracking until its removal in v10 (#9094)
• Reset appHangTimeoutInterval values of 0 or lower to the default of 2 seconds, which previously spun the app hang tracker thread in a busy loop (#9020)
• Release App Hang tracking listener wrappers when listeners are removed (#9127)

9.29.0

Warning

Native crashes now set mechanism.synthetic, which takes the mach exception name (EXC_BAD_ACCESS) or signal name (SIGSEGV) out of the grouping hash. Expect a one-time regrouping as your app adopts this version: existing crash issues stop receiving events and new ones open. Crashes that differ only by signal at the same stacktrace now share one issue. The mach and signal detail stays on mechanism.meta.

Fixes

• Store the binary image cache in zero-fill memory to reduce the SDK binary size. (#9003)
• Fix crash in [NSURLSessionTask cancel] when cancelling an in-flight task with swizzling enabled (#9009)
• Clear the scope's replayId when Session Replay is stopped manually, so events captured after stop() are no longer linked to a replay that is no longer recording (#9017)
• Mark the fabricated mach and signal crash mechanisms as synthetic so an Apple crash groups with the identical crash reported by the other Sentry SDKs (#9004)
• Set mechanism.handled to false on crash reports without mach context, which previously left it unset (#9004)
• Sample and flush Session Replay when the feedback form opens or feedback is captured manually, preserving the form's opening-time replay association even if the session changes before submission (#9046)

Deprecations

• Deprecate legacy App Hang tracking because it can produce less relevant stack traces and false positives. Enable the MetricKit integration for system-provided hang diagnostics by setting options.enableMetricKit = true. The appHangTimeoutInterval option remains supported for watchdog termination classification. (#8944)

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 8691940. Configure here.}

[sentry]

Bug: The code uses PrivateSentrySDKOnly, which is deprecated in Sentry Cocoa 9.26.1. This will become a breaking change in a future major version.
_{Severity: MEDIUM}

Suggested Fix

Migrate all calls from the deprecated PrivateSentrySDKOnly to the new SentrySDK.internal equivalents. For example, replace PrivateSentrySDKOnly.setSdkName() with SentrySDK.internal.sdk.setName() and PrivateSentrySDKOnly.installationID with SentrySDK.internal.sdk.installationID. This will resolve the deprecation warnings and prevent breaking changes in future major versions of the Sentry Cocoa SDK.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.

Location: Package.swift#L14

Potential issue: The pull request updates the Sentry Cocoa SDK to version 9.26.1 but
continues to use the `PrivateSentrySDKOnly` API, which has been deprecated in favor of
`SentrySDK.internal`. While the deprecated API remains functional in the 9.x series and
will only produce compile-time warnings, it is scheduled for removal in the next major
version (10.0.0). This introduces a maintenance debt that will lead to a breaking change
and compilation failures once the dependency is updated to version 10.0.0 or later. The
code should be migrated to the new APIs to ensure future compatibility.

Also affects:

• SentryCapacitor.podspec:15~15