Migration Guide
To upgrade from version 4.x of the SDK to version 9.x of the SDK, you must first migrate from 4.x to 5.x, then 5.x to 6.x, then 6.x to 7.x, 7.x to 8.x, and finally from 8.x to 9.x.
Migrating to 9.x from 8.x includes several breaking changes. We provide this guide to help you update your SDK.
We bumped the minimum supported OS versions to:
- iOS: 15.0 (previously 11.0)
- macOS: 10.14 (previously 10.13)
- tvOS: 15.0 (previously 11.0)
- visionOS: 1.0 (unchanged)
- watchOS: 8.0 (previously 4.0)
We now build the precompiled XCFramework with Xcode 16. To submit to the App Store, Apple now requires Xcode 16. If you need a precompiled XCFramework built with Xcode 15, continue using Sentry SDK 8.x.x.
Additionally, the Package.swift sets swift-tools-version to 6.0.
We dropped official support for Carthage in v9. If you're using Carthage, please migrate to Swift Package Manager (SPM) or manually install the pre-built XCFramework from GitHub releases.
We now enabled the following features by default:
- Performance V2 is enabled by default: The app start duration now finishes when the first frame is drawn instead of when the OS posts the
UIWindowDidBecomeVisibleNotification. We removed theenablePerformanceV2option. - Pre-warmed app start tracking: The SDK now collects pre-warmed app starts by default via
enablePreWarmedAppStartTracing. - App hang tracking V2: This is now the default only on **iOS and tvOS and we removed the option to enable/disable it. macOS still uses V1.
We now automatically disable app hang tracking for: Widgets, Live Activities, Action Extensions, (Siri) Intent Extensions, Share Extensions. These components run in separate processes or sandboxes with different execution characteristics, which can cause false positive app hang reports.
We moved structured logging out of experimental and made it part of the stable API. The enableLogs option moved from options.experimental.enableLogs to options.enableLogs. We added log APIs to Hub and Client, and logs now include a sentry.replay_id attribute.
Migration required: Update your code from options.experimental.enableLogs = true to options.enableLogs = true. Logging is not enabled by default; you must explicitly set this option.
HTTP client errors now mark sessions as errored. This provides better visibility into failed network requests in your release health data.
We removed all deprecated profiling APIs in version 9.0.0.
enableFileManagerSwizzlingis now a top-level non-experimental option and remains disabled by default.enableDataSwizzlingis now a top-level option and is enabled by default.enableLogsis now a top-level non-experimental option and remains disabled by default (you must set it totrueto enable logging).- We increased the maximum attachment size to 200MB (previously 20MB)
- We removed the following methods and properties:
inAppExclude(it had no effect)integrationsdefaultIntegrations()enableTracing(usetracesSampleRateortracesSamplerinstead)getStoreEndpoint()enablePerformanceV2the behavior of this option is now enabled by default.
- The default trace context status is now
okinstead ofundefined. - The
functionproperty onSentryFramenow defaults tonilinstead of"<redacted>" - The
valueandtypeproperties onSentryExceptionare now nullable; whenNSExceptionhas no reason,typeis set tonil - We changed the type of the
http.response.status_codeattribute for spans to int - We converted
SentryDsnto Swift and removed the public header fileSentryDsn.h
- We renamed
SentryStructuredLogLeveltoSentryLogLevel - We renamed
SentryStructuredLogAttributetoSentryLogAttribute
- We removed the
segmentproperty fromSentryTraceContext,SentryUser, andSentryBaggage - We removed the initializers from
SentryTraceContext - We removed
SentryDsn.getHash() - We removed
SentryFrame.instruction
We removed the following deprecated APIs:
SentrySpan.setExtraValue(_:forKey:)- User feedback API (use the new feedback API instead)
Scope.useSpan()(useScope.spaninstead)SentryDebugMeta.uuid(usedebugIDinstead)SentryDebugMeta.name(usecodeFileinstead)
We made the following classes and APIs private:
SentryEventDecoderandSentryEventDecodableSentryEnvelopeItemHeaderSentryIntegrationProtocolSentrySessionSentrySDKInfoSentryDebugImageProvider
- We made the following classes
final:PreviewRedactOptions,SentryProfileOptions,SentryRedactViewHelper,SentryViewScreenshotOptions,SentryReplayOptions,SentryUserFeedbackConfiguration,SentryUserFeedbackFormConfiguration,SentryUserFeedbackThemeConfiguration,SentryUserFeedbackWidgetConfiguration,SentryFeedback, andSentryExperimentalOptions
For a complete list of changes, see the Changelog of version 9.0.0
Migrating to 8.x from 7.x includes a few breaking changes. We provide this guide to help you update your SDK. It's important to note that this version adds a dependency to Swift, and that we renamed the default branch on the sentry-cocoa repository from master to main.
The minimum supported OS versions have been bumped to macOS 10.13, iOS 11, tvOS 11, and watchOS 4. We bumped the minimum Xcode version to 13.
The following features are now enabled by default:
- The user interaction tracing integration
- The File I/O tracing integration
- Core Data tracing integration
- Capture failed requests
- App Hangs (not available for watchOS)
App Hang events might group differently as we now set the event stack trace snapshot property to true.
The OOM (out of memory integration) actually tracks watchdog terminations based on heuristics. We renamed the integration to better reflect what it does.
This version includes the following configuration changes:
- Rename
SentryOptions.enableAutoPerformanceTrackingtoSentryOptions.enableAutoPerformanceTracing - Rename
SentryOptions.enableUIViewControllerTrackingtoSentryOptions.enableUIViewControllerTracing - Rename
SentryOptions.enablePreWarmedAppStartTrackingtoSentryOptions.enablePreWarmedAppStartTracing - Rename
SentryOptions.enableFileIOTrackingtoSentryOptions.enableFileIOTracing - Rename
SentryOptions.enableCoreDataTrackingtoSentryOptions.enableCoreDataTracing - Rename
SentryOptions.enableOutOfMemoryTrackingtoSentryOptions.enableWatchdogTerminationTracking
We made some changes to make the API more ergonomic in Swift:
- Rename
SentrySDK.addBreadcrumb(crumb:)toSentrySDK.addBreadcrumb(_ crumb:) - Rename
SentryScope.add(_ crumb:)toSentryScope.addBreadcrumb(_ crumb:) - Rename
SentryScope.add(_ attachment:)toSentryScope.addAttachment(_ attachment:) - Rename
ClienttoSentryClient
We cleaned up our public classes by removing a few functions and properties, that shouldn't be public, to make the API cleaner. In case we removed something you need, please open an issue on GitHub.
- Make
SpanProtocol.datanon nullable - Mark
[SpanProtocol setExtraValue:forKey:]as deprecated - Make
SpanContextimmutable- Remove tags from
SpanContext - Remove context property from
SentrySpan
- Remove tags from
- Remove
SentryScope.apply(to:) - Remove
SentryScope.apply(to:maxBreadcrumb:) - Remove
[SentryOptions initWithDict:didFailWithError:] - Remove
[SentryOptions sdkInfo] - Make
SentrySessionandSentrySDKInfointernal - Remove default attachment content type
- Remove
captureEnvelopefromSentryHubandSentryClient - Remove confusing transaction tag
We removed the version of SentrySDK.startWithOptions that took a dictionary, and renamed SentrySDK.startWithOptionsObject to SentrySDK.startWithOptions. The recommended way to initialize Sentry has not changed:
import Sentry
SentrySDK.start { options in
options.dsn = "___PUBLIC_DSN___"
// ...
}
SentrySDK.close now calls flush, which is a blocking call.
Important
We recommend updating to at least 7.5.3, because the HTTP instrumentation can lead to crashes. Alternatively, you can also disable the feature.
Migrating to 7.x from 6.x includes a few breaking changes. We provide this guide to help you to update your SDK.
This version includes the following configuration changes:
- Change the default maximum number of cached envelopes from 100 to 30. You can now configure this number with
SentryOptions.maxCacheItems. - When setting a value
SentryOptions.sampleRatethat is not >= 0.0 and <= 1.0 the SDK sets it to the default of 1.0 instead of keeping the set value.
This version introduces a change to the grouping of issues. The SDK now sets the inApp flag for frames originating from only the main executable using CFBundleExecutable. In previous versions, all frames originating from the application bundle were marked as inApp. This had the downside of marking frames of private frameworks inside the bundle as inApp. This problem is fixed now. Applications using static frameworks shouldn't be affected by this change. For more information read mark in-app frames.
We cleaned up our public classes by removing a few functions and properties, that shouldn't be public, to make the API cleaner. In case we removed something you need, please open an issue on GitHub.
- Remove
SentrySDK.currentHubandSentrySDK.setCurrentHub. - Remove
SentryClient.storeEnvelope, which is reserved for Hybrid SDKs. - Make
closeCachedSessionWithTimestampprivate, which is reserved for internal use. - Remove deprecated
SentryHub.getScope. UseSentryHub.scopeinstead. - Replace
SentryException.threadwithSentryException.threadIdandSentryException.stacktraceto align with the unified API. - Replace dict
SentryMechanism.metawith new classSentryMechanismMetaand moveSenryNSErrortoSentryMechanismMetato align with the unified API. - Change
SentryEvent.timestamptonullable.
We replaced the SentryLogLevel with SentryLevel, renamed logLevel to diagnosticLevel on SentryOptions to align with other Sentry SDKs, and set the default diagnosticLevel to SentryLevel.debug. Furthermore, we removed setting the logLevel statically on the SentrySDK. Please use the SentryOptions to set the diagnosticLevel instead.
6.x
SentrySDK.start { options in
options.logLevel = SentryLogLevel.verbose
}
// Or
SentrySDK.logLevel = SentryLogLevel.verbose
7.x
SentrySDK.start { options in
options.diagnosticLevel = SentryLevel.debug
}
Migrating to 6.x from 5.x includes a few breaking changes. We provide this guide to help you to update your SDK.
This version includes the following configuration changes:
- Auto Session Tracking is enabled by default. This feature is collecting and sending health data about the usage of your application.
- Attach stack traces is enabled per default.
- We bumped the minimum iOS version to 9.0.
- Use a BOOL in SentryOptions instead of NSNumber to store booleans.
- We had previously removed the enabled option from SentryOptions, but we brought it back in version 6.0.7 with slightly changed functionality. Previously setting an empty or incorrect DSN also set
enabledtofalse. This side effect is removed. Setting the DSN has no impact onenabled. If the DSN is nil or empty orenabledis set tofalseand the client won't send any data to Sentry.
This version uses the envelope endpoint. If you are using self-hosted Sentry, you must use Sentry version >= v20.6.0 or higher. If you are using sentry.io, there is no impact. For this change, we also now cache events in envelopes on the disk. We decided not to migrate the few cached events from 5.x to 6.x into envelopes. Instead, we remove them from the disk. As a result, you might lose a few cached events when upgrading.
We removed the deprecated SDK inits. The recommended way to initialize Sentry is now:
import Sentry
SentrySDK.start { options in
options.dsn = "___PUBLIC_DSN___"
// ...
}
We cleaned up our public headers and made most of our classes private. If you can't access one of the classes you need please open an issue and tell us your use case so we can evaluates whether to either make the class public again or provide another API for you.
In 5.x, we used a nullable NSString to represent an event ID. The SDK, Hub, and Client returned this nullable NSString for the event ID to capture messages, events, errors, and so forth. In 6.x, we have a new type SentryId, which is not nullable, to represent an event ID. Instead of returning nil when an event couldn't be queued for submission we return SentryId.empty.
Example in 5.x:
import Sentry
let eventId = SentrySDK.capture(message: "A message")
if (nil != eventId) {
// event was queued for submission
} else {
// event wasn't queued for submission
}
Example in 6.x:
import Sentry
let eventId = SentrySDK.capture(message: "A message")
if (eventId != SentryId.empty) {
// event was queued for submission
} else {
// event wasn't queued for submission
}
In 6.x, we introduce a new type SentryMessage for event.message. SentryMessage provides you the ability to pass a format string with parameters to Sentry, which can help group similar messages into the same issue.
Example in 5.x:
import Sentry
let event = Event()
event.message = "Hello World"
Example in 6.x:
import Sentry
let event = Event()
event.message = SentryMessage(formatted: "Hello World")
In 5.x, you could pass a nullable scope to capture methods of the SDK, Hub, and Client, such as SentrySdk.captureMessage(). In 6.x, we changed the Scope to nonnull and provide overloads for the Hub and the Client.
Please see the Changelog for a complete list of changes.
The samples below illustrate how the SDK works:
Example in 4.x:
do {
Client.shared = try Client(dsn: "___PUBLIC_DSN___")
try Client.shared?.startCrashHandler()
} catch let error {
print("\(error)")
}
Example in 5.x:
SentrySDK.start(options: [
"dsn": "___PUBLIC_DSN___",
"debug": true
])
Example in 4.x:`
Client.shared?.breadcrumbs.add(Breadcrumb(level: .info, category: "test"))
Example in 5.x:
SentrySDK.addBreadcrumb(Breadcrumb(level: .info, category: "test"))
Example in 4.x:
let event = Event(level: .debug)
event.message = "Test Message"
event.environment = "staging"
event.extra = ["ios": true]
Client.shared?.send(event: event)
Example in 5.x:
SentrySDK.capture(message: "Test Message") { (scope) in
scope.setEnvironment("staging")
scope.setExtras(["ios": true])
let u = Sentry.User(userId: "1")
u.email = "tony@example.com"
scope.setUser(u)
}
Example in 4.x:
let u = User(userId: "1")
u.email = "tony@example.com"
Client.shared?.user = user
Example in 5.x:
let u = Sentry.User(userId: "1")
u.email = "tony@example.com"
SentrySDK.setUser(u)
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").