Skip to content

chore(deps): update dependency sentry to v9.25.0 - #484

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/sentry-9.x
Open

chore(deps): update dependency sentry to v9.25.0#484
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/sentry-9.x

Conversation

@renovate

@renovate renovate Bot commented Jun 3, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
Sentry from minor 9.15.09.25.0

Release Notes

getsentry/sentry-cocoa (Sentry)

v9.25.0

Compare Source

[!WARNING]
This release raises the minimum deployment targets to macOS 12 and watchOS 9. Apps that support older OS versions must use an earlier Sentry Cocoa release.

Breaking Changes
  • Bump the minimum deployment targets to macOS 12 and watchOS 9 because Xcode 27 no longer supports earlier versions. This lets the SDK adopt Xcode 27 without blocking users from building and submitting their apps with the latest Xcode. (#​8595, #​8113, #​8189)
Features
  • Add SentrySDK.feedback.enableOnShake() and disableOnShake() to toggle the shake-to-report gesture at runtime (#​8591)
Fixes
  • Reduce memory usage when storing envelopes with large attachments (#​8649)
  • Fix incorrect duration sent for active sessions (#​8612)
    • Session duration is now set only when the session ends. Active sessions (including on error increments) no longer emit a bogus duration.
  • Fix a race that could prevent consecutive app hangs from being reported (#​8627)
  • Fix malformed itms-services URL in SentryDistribution updater (#​8567)
  • Fix off-main thread reads of -[UIApplication applicationState] (8672)

v9.24.0

Compare Source

[!IMPORTANT]
Due to a potential risk of revealing PII or security-relevant data in crash events in specific circumstances, we're shipping this strictly speaking breaking change in a minor version.

Breaking Changes
  • Add enableMemoryIntrospection option to allow users to control memory introspection in crash reports, defaults to false (was previously true) (#​8571)
    • You can re-enable this feature by setting the option enableMemoryIntrospection to true
    • When this option is disabled, string stack contents found near the crash site will not be included in the event sent to Sentry. These contents are displayed in the 'message' subtitle shown underneath the main issue title in Sentry.
Features
  • Add Breadcrumb.setData(value:key:) to set a single breadcrumb data entry and deprecate the Breadcrumb.data setter in its favor. (#​8572)
Fixes
  • Fix screenshots not being captured by hybrid SDKs (#​8578)
  • Fix trace propagation for manually instrumented transactions when automatic performance tracing is disabled (#​8522)
  • Prevent a Session Replay crash (NSInvalidArgumentException / -[NSConcreteValue doubleValue]) when Core Animation raises while redacting the view hierarchy, e.g. during React Navigation transitions or video fullscreen presentation (#​8537)
  • Remove x/y coordinates from UI breadcrumbs, as they are a potential security risk, for example leaking input on custom PIN code views (#​8534)

v9.23.0

Compare Source

Features
  • Record trace_metric_byte client reports (#​8490)
Fixes
  • Add a depth limit to view hierarchy serialization to prevent a stack overflow crash on deeply nested view hierarchies (#​8292)
  • Persist the configured environment in crash reports so later app launches don't overwrite it (#​8511)
  • Only expose experimental.dataCollection APIs in SDK V10 (#​8435)
Improvements
  • Reduce slight overhead during SDK start by skipping an unnecessary main thread dispatch when there's no work to do (#​8494)

v9.22.0

Compare Source

Features
  • Mark opt in option swiftAsyncStacktraces as stable (#​8373)
  • Add dataCollection option under experimental for configuring data scrubbing behavior (#​8369)
  • Add scope API to clear feature flags (#​8364)
  • Add dictionary initialization for options.experimental.dataCollection (#​8371)
Fixes
  • Session Replay now correctly reads the response Content-Type for HTTP/2 and HTTP/3, so it captures HTTP response bodies as it was supposed to (when body capturing is enabled via options.sessionReplay.networkCaptureBodies) (#​8390)
  • Log the actual request error instead of (null) when a Spotlight request fails (#​8401)
  • Decoding dictionary to Options sets value of key "dsn" to property dsn instead of nil (#​8393)
Improvements
  • Remove enableReplayNetworkDetailsCapturing experimental flag; network detail capture is now enabled automatically when networkDetailAllowUrls is non-empty (#​8396)

v9.21.0

Compare Source

Fixes
  • Fix use-after-free race in span, startProfiler, and stopProfiler by snapshotting currentHub under currentHubLock before dereferencing. (#​8318)
  • Add userInfo context for unhandled NSExceptions (#​8332)
Features
  • Attach feature flag evaluations to active spans (#​8158)
  • Add feature flag scope ObjC API (#​8160)

v9.20.0

Compare Source

[!IMPORTANT]
This release contains an important fix for dropping too much data when the SDK gets rate limited. (#​8324) This fix changes how rate limits are handled. Previously, if one data type (for example, user feedback) was rate limited, other data such as spans or sessions could also be dropped. Now, only the rate-limited data is dropped, while all other data continues to be sent. This may also reduce cases where unexpectedly large amounts of data appear to be dropped due to rate limiting.

Fixes
  • Fix rate limiting all data categories when data category rate-limit is active. (#​8324)
Features
  • Record log_byte client reports (#​8186)
  • Add scope feature flag API (#​8147)
Fixes
  • Fix EXC_BAD_ACCESS in SentryNetworkTracker caused by repeated reads of the volatile NSURLSessionTask.currentRequest property (#​8058)

v9.19.1

Compare Source

Fixes
  • Fix use-after-free crash in SentrySDKInternal.isEnabled (#​8310)
  • Fix dropped platform item header in profile-chunk envelopes (#​8269)
  • Fix crash report ID generation so reports created at certain timestamps are not ignored (#​8216)
  • Fix C++ exception capture on newer OS versions by page-aligning mprotect calls in the __cxa_throw swapper (#​8221)
  • Fix client report discarded-event counts for categories reported in quantities greater than one (e.g. spans): each drop now adds the full dropped quantity instead of incrementing by one (#​8230)
  • Rename extended app start span operation from app.start.extended_app_start to app.start.extended (#​8220)
  • Fix unsynchronized debug-mode access in the binary image cache (#​8309)

v9.19.0

Compare Source

[!WARNING]
The minimum macOS deployment target will be raised to macOS 12 (Monterey) with the upcoming release that adopts Xcode 27. Xcode 27 no longer supports deployment targets below macOS 12. If your app must support macOS 11 or earlier, please stay on the last SDK version released before this change. See #​8113 for full details.

Features
  • Renamed experimental extended app start API (#​8161):
    • extendAppLaunch() -> extendAppStart()
    • finishExtendedAppLaunch() -> finishExtendedAppStart()
    • Added getExtendedAppStartSpan() to get the extended app span
  • Add extended app start APIs to ObjC wrapper SDK (#​8163)
Improvements
  • Reduce Session Replay capture stutters by scheduling screenshots after run loop UI work instead of from display refresh callbacks (#​7851)
Fixes
  • Don't send logs and metrics when the SDK is disabled (#​8173)
  • Fixes crash caused by modifying breadcrumbs from multiple threads (#​8114)
  • Prevent feedback form on external displays (#​8071)
  • Keep the User Feedback screenshot trigger active after form dismissal. (#​8048)
  • Prevent lazy TLS-init in the signal crash monitor for non-managed runtime builds (#​8148)
  • Include breadcrumbs in recovered buffer-mode session replays (#​8153)
  • Fix missing Info.plist entries MinimumOSVersion and CFBundleSupportedPlatforms in SentryObjC.xcframework (#​8157)
  • Harden crash-time attachment path creation to avoid secondary crashes while handling crashes (#​8170)
  • Session replay video assembly: drop empty video segments, avoid duplicating frames at segment boundaries, and keep video timing stable when captured frames are skipped or unreadable (#​8041)
Internal
  • Add SentrySDK.internal structured API for hybrid SDKs, replacing PrivateSentrySDKOnly with namespaced sub-APIs (replay, profiling, appStart, performance, screenshot, viewHierarchy, screen, envelope, swizzle, sdk, debug, breadcrumbs, user) (#​8097)

v9.18.0

Compare Source

Features
  • Add SentryObjC User Feedback presentation APIs and a feedback form factory returning UIViewController instances. (#​8027)
Fixes
  • Show feedback form from shake or screenshot without widget (#​8050)
Deprecations
  • Deprecate the managed User Feedback custom button. It will be removed in v10. Present the feedback form from your own UI with SentrySDK.feedback.show(), SentrySDK.FeedbackForm, or .sentryFeedback(isPresented:) instead. (#​8052)

v9.17.1

Compare Source

Fixes
  • Ship dSYMs in SentryObjC-Dynamic.xcframework artifacts (#​8036)
  • Fix missing _OBJC_CLASS_$_ symbols in x86_64 slice of SentryObjC dynamic framework (#​8037)
  • Mark feedback form aliases and conformances unavailable in app extensions (#​8040)
  • Silence retroactive conformance warning for SentryLevel: CustomStringConvertible when building with SPM from source (#​8032)

v9.17.0

Compare Source

Features
  • Support creating envelope items from attachments via SentryObjC (#​8001)

  • Add format-string logging to SentryObjCLogger with automatic message template extraction (#​7996)

    [SentryObjCSDK.logger infoWithFormat:@"User %@ processed %d items", userName, count];
  • Add managed user feedback form presentation APIs (#​7873)

    Apps using the managed User Feedback integration can now present the form directly:

    • Use SentrySDK.feedback.show() to let the SDK pick the best presenter.
    • In UIKit, present the SentrySDK.FeedbackForm() view controller yourself.
    • In SwiftUI, use .sentryFeedback(isPresented:), or present SentrySDK.FeedbackFormView() from a container such as .sheet.

    These APIs use the global SentryOptions.configureUserFeedback configuration and temporarily hide the managed widget
    while the form is open, when possible.

  • Add per-form feedback configuration (#​8018)

    Managed feedback presentation APIs now accept a configuration closure, so apps can customize a single
    form on top of the global SentryOptions.configureUserFeedback settings without mutating them:

    SentrySDK.feedback.show { config in
        config.configureForm = { form in
            form.formTitle = "Report a Bug"
            form.submitButtonLabel = "Send Report"
        }
        config.tags = ["screen": "settings"]
    }
  • Standalone app start sub-spans operations have been renamed for better clarity (#​8003):

    • Pre Runtime Init: app.start -> app.start.pre_runtime_init
    • Runtime Init to Pre Main Initializers: app.start -> app.start.runtime_init
    • UIKit Init: app.start -> app.start.uikit_init
    • Application Init: app.start -> app.start.application_init
    • Extended App Start: app.start -> app.start.extended_app_start
Deprecations
  • Deprecate the managed User Feedback widget/FAB. It will be removed in v10. Present the feedback form from your own UI with SentrySDK.feedback.show(), SentrySDK.FeedbackForm, or .sentryFeedback(isPresented:) instead. (#​8022)
Fixes
  • App start duration on the Vitals dashboard now reflects the extended app launch time when using extendAppLaunch() (#​8028)

v9.16.1

Compare Source

[!NOTE]
No documented changes. This is the same as 9.16.0, re-released to fix the SentryObjC-Static SPM checksum.

[!IMPORTANT]
The new SentryObjC SDK introduced in this release should be considered experimental and may be subject to breaking changes.

Features
  • Add SentryObjC wrapper SDK — a pure Objective-C interface for projects that cannot enable Clang modules (e.g., ObjC++ with -fmodules=NO). (#​7918)

    Ships as a compile-from-source SPM product SentryObjC, a static pre-compiled framework SentryObjC-Static.xcframework.zip and a dynamic pre-compiled framework SentryObjC-Dynamic.xcframework.zip.

    Steps to migrate:

    • Replace your dependency on the target Sentry or SentrySPM with SentryObjC (or SentryObjC-Static / SentryObjC-Dynamic if you want to use the precompiled binary targets).
    • Change #import <Sentry/Sentry.h> to #import <SentryObjC/SentryObjC.h>
    • Rename Sentry-prefixed types to SentryObjC (e.g., SentrySDKSentryObjCSDK, SentryOptionsSentryObjCOptions).
  • SentrySDK.extendAppLaunch() now returns the extended app launch span, allowing users to add child spans for granular breakdown of the app start period (#​7985)

Fixes
  • Fix crash in SentryFramesTracker.add/removeListener when called from a listener's own init / deinit on a background thread, observed on iOS 26 (#​7943)
  • Report only cold or warm as start_type for standalone app starts, removing the .prewarmed suffix per sentry-conventions (#​7968)
  • Fix reporting arbitrary Objective-C object throws via the C++ exception monitor (#​7984)

v9.16.0

Compare Source

[!WARNING]
The SentryObjC-Static SPM binary target in this release has an incorrect checksum and resolving dependencies might fail, but the release artifacts are not affected.

[!IMPORTANT]
The new SentryObjC SDK introduced in this release should be considered experimental and may be subject to breaking changes.

Features
  • Add SentryObjC wrapper SDK — a pure Objective-C interface for projects that cannot enable Clang modules (e.g., ObjC++ with -fmodules=NO). (#​7918)

    Ships as a compile-from-source SPM product SentryObjC, a static pre-compiled framework SentryObjC-Static.xcframework.zip and a dynamic pre-compiled framework SentryObjC-Dynamic.xcframework.zip.

    Steps to migrate:

    • Replace your dependency on the target Sentry or SentrySPM with SentryObjC (or SentryObjC-Static / SentryObjC-Dynamic if you want to use the precompiled binary targets).
    • Change #import <Sentry/Sentry.h> to #import <SentryObjC/SentryObjC.h>
    • Rename Sentry-prefixed types to SentryObjC (e.g., SentrySDKSentryObjCSDK, SentryOptionsSentryObjCOptions).
  • SentrySDK.extendAppLaunch() now returns the extended app launch span, allowing users to add child spans for granular breakdown of the app start period (#​7985)

Fixes
  • Fix crash in SentryFramesTracker.add/removeListener when called from a listener's own init / deinit on a background thread, observed on iOS 26 (#​7943)
  • Report only cold or warm as start_type for standalone app starts, removing the .prewarmed suffix per sentry-conventions (#​7968)
  • Fix reporting arbitrary Objective-C object throws via the C++ exception monitor (#​7984)

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot changed the title chore(deps): update dependency sentry to v9.16.1 chore(deps): update dependency sentry to v9.17.0 Jun 10, 2026
@renovate
renovate Bot force-pushed the renovate/sentry-9.x branch from 39c15e6 to 24fb574 Compare June 10, 2026 18:03
@renovate renovate Bot changed the title chore(deps): update dependency sentry to v9.17.0 chore(deps): update dependency sentry to v9.17.1 Jun 11, 2026
@renovate
renovate Bot force-pushed the renovate/sentry-9.x branch 2 times, most recently from 57087d7 to d1ae73a Compare June 18, 2026 18:00
@renovate renovate Bot changed the title chore(deps): update dependency sentry to v9.17.1 chore(deps): update dependency sentry to v9.18.0 Jun 18, 2026
@renovate renovate Bot changed the title chore(deps): update dependency sentry to v9.18.0 chore(deps): update dependency sentry to v9.19.0 Jun 24, 2026
@renovate
renovate Bot force-pushed the renovate/sentry-9.x branch from d1ae73a to c7d7b8c Compare June 24, 2026 21:39
@renovate renovate Bot changed the title chore(deps): update dependency sentry to v9.19.0 chore(deps): update dependency sentry to v9.19.1 Jul 1, 2026
@renovate
renovate Bot force-pushed the renovate/sentry-9.x branch from c7d7b8c to 9fd93f6 Compare July 1, 2026 23:07
@renovate renovate Bot changed the title chore(deps): update dependency sentry to v9.19.1 chore(deps): update dependency sentry to v9.20.0 Jul 6, 2026
@renovate
renovate Bot force-pushed the renovate/sentry-9.x branch from 9fd93f6 to ac08530 Compare July 6, 2026 17:15
@renovate renovate Bot changed the title chore(deps): update dependency sentry to v9.20.0 chore(deps): update dependency sentry to v9.21.0 Jul 8, 2026
@renovate
renovate Bot force-pushed the renovate/sentry-9.x branch from ac08530 to 871f9fc Compare July 8, 2026 18:16
@renovate renovate Bot changed the title chore(deps): update dependency sentry to v9.21.0 chore(deps): update dependency sentry to v9.22.0 Jul 15, 2026
@renovate
renovate Bot force-pushed the renovate/sentry-9.x branch from 871f9fc to 0883a72 Compare July 15, 2026 17:30
@renovate
renovate Bot force-pushed the renovate/sentry-9.x branch from 0883a72 to 32a06e4 Compare July 22, 2026 21:39
@renovate renovate Bot changed the title chore(deps): update dependency sentry to v9.22.0 chore(deps): update dependency sentry to v9.23.0 Jul 22, 2026
@renovate renovate Bot changed the title chore(deps): update dependency sentry to v9.23.0 chore(deps): update dependency sentry to v9.24.0 Jul 30, 2026
@renovate
renovate Bot force-pushed the renovate/sentry-9.x branch from 32a06e4 to e464cb7 Compare July 30, 2026 08:20
@renovate
renovate Bot force-pushed the renovate/sentry-9.x branch from e464cb7 to 4604048 Compare August 5, 2026 18:57
@renovate renovate Bot changed the title chore(deps): update dependency sentry to v9.24.0 chore(deps): update dependency sentry to v9.25.0 Aug 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants