Skip to content

chore(deps): update Cocoa SDK to v9.27.0 - #2830

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
deps/modules/sentry-cocoa/9.27.0
Open

chore(deps): update Cocoa SDK to v9.27.0#2830
github-actions[bot] wants to merge 1 commit into
mainfrom
deps/modules/sentry-cocoa/9.27.0

Conversation

@github-actions

@github-actions github-actions Bot commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

Bumps modules/sentry-cocoa from 9.26.1 to 9.27.0.

Auto-generated by a dependency updater.

Changelog

9.27.0

Note

enableLogs and enableMetrics are now deprecated and will be removed in the next major version. Manual log and metric capture is no longer gated by these flags.

Improvements

  • Install idle Session Replay recovery infrastructure at zero sample rates. (#8865)
  • Manual log and metrics APIs are no longer gated by behind enableLogs / enableMetrics (#8918)

Features

  • Add manual Session Replay controls through SentrySDK.replay. (#8868)
    • Explicit start() and startBuffering() calls bypass the configured replay sample rates; sampling still controls automatic startup.
    • start() starts a full-session replay and does nothing if one is already recording.
    • startBuffering() keeps a rolling buffer that is sent on flush() or an error, then continues in session mode.
    • stop() ends the current replay; the next start() creates a new replay session.
    • pause() suspends recording until resume() and remains paused across background and foreground transitions and automatic replay restarts in the same process.
    • resume() continues the same manually paused replay.
    • flush() sends the current replay data to Sentry, or starts a full-session replay when recording is stopped.

Improvements

  • Install idle Session Replay recovery infrastructure at zero sample rates. (#8865)

Features

  • Copy app.vitals.start.type and app.vitals.start.screen onto standalone app.start children, including app.start.extended and user descendants (#8888)
  • Add maxFeatureFlags option to configure how many feature flag evaluations the scope retains, matching sentry-java. Defaults to 100 (#8858)
  • Add SentrySDK.internal.envelope.captureNonTerminating for hybrid SDKs, which keeps the current session running and reports it with the unhandled status when an unhandled exception doesn't terminate the process (#8654)
  • Add SentrySDK.internal.envelope.updateSessionForDroppedEventNonTerminating so hybrid SDKs can update the native session when an error is dropped by sampling, without sending an envelope (#8907)

Fixes

  • Silence spurious ERROR log in SentryCrashCxaThrowSwapper for empty sections (#8915)
  • Stop recording touch events while Session Replay is paused. (#8887)

Internal

  • Add visionOS support to internal screen APIs (#8913)

@bruno-garcia
bruno-garcia force-pushed the deps/modules/sentry-cocoa/9.27.0 branch from a50654a to aa3e83d Compare September 4, 2026 03:02
Comment thread modules/sentry-cocoa
@@ -1 +1 @@
Subproject commit a00a9784fff7193cbb0f9fae509fec8107e07744
Subproject commit aaf96c4a417d30208b3c25d90910d6156ddc973d

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: The Unity wrapper passes deprecated enableLogs and enableMetrics flags to the Cocoa SDK, which now ignores them, creating a configuration mismatch and potential for unintended data capture.
Severity: LOW

Suggested Fix

The bridge should stop passing the deprecated enableLogs and enableMetrics options to the Cocoa SDK, as they are now no-ops. Alternatively, this change in behavior and the deprecation of these flags should be clearly documented for users to prevent confusion.

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: modules/sentry-cocoa#L1

Potential issue: The update to Cocoa SDK 9.27.0 deprecates the `enableLogs` and
`enableMetrics` flags, meaning they no longer control log or metric capture in the
native iOS layer. However, the Unity bridge continues to pass these options from the C#
layer. While the C# code currently gates features using these flags, this creates a
discrepancy. If a user sets `options.EnableLogs = false`, they expect no logs to be
captured. But if any native Cocoa code attempts to capture logs or metrics directly, it
will succeed because the native SDK no longer respects the deprecated flag, leading to
unexpected data capture.

Did we get this right? 👍 / 👎 to inform future reviews.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant