Changelog

8.9.3

Fixes

8.9.2

Improvements

Fixes

8.9.1

Fixes

8.9.0

Features

This change considerably speeds up retrieving stacktraces, which the SDK uses for captureMessage, captureError and also for reporting file IO or DB operation on the main thread.

Breaking change

8.9.0-beta.1

Features

8.8.0

Features

Fixes

8.7.4

Fixes

Breaking Changes

8.7.3

Fixes

8.7.2

Fixed

8.7.1

Fixes

8.7.0

Features

enum LoginError: Error {
    case wrongUser(id: String)
    case wrongPassword
}

SentrySDK.capture(error: LoginError.wrongUser("12345678"))

For the Swift error above Sentry displays:

sentry-cocoa SDK Title Description
Since 8.7.0 LoginError wrongUser(id: "12345678") (Code: 1)
Before 8.7.0 LoginError Code: 1

Customized error descriptions have precedence over this feature. This change has no impact on grouping of the issues in Sentry.

Fixes

8.6.0

Features

Trace origin indicates what created a trace or a span. Not all transactions and spans contain enough information to tell whether the user or what precisely in the SDK created it. Origin solves this problem. The SDK now sends origin for transactions and spans.

Fixes

Removed

The stitchAsyncCode experimental option has been removed from SentryOptions as its behavior was unpredictable and sometimes resulted in unexpected errors. We plan to add it back once we fix it, but we don't have an ETA for it.

8.5.0

Features

Fixes

8.4.0

Features

Fixes

8.3.3

Fixes

8.3.2

Features

Fixes

Improvements

8.3.1

Fixes

8.3.0

Important Note

This release can cause crashes when Profiling is enabled (#2779). Please update to 8.3.1.

Fixes

8.2.0

Features

Fixes

Improvements

This change might mark 3rd party library frames as in-app, which the SDK previously marked as system frames.

8.1.0

Features

Fixes

8.0.0

Features

This version adds a dependency on Swift. We renamed the default branch from master to main. We are going to keep the master branch for backwards compatibility for package managers pointing to the master branch.

Features

Fixes

Breaking Changes

7.31.5

Fixes

7.31.4

Fixes

7.31.3

Fixes

7.31.2

Fixes

7.31.1

Fixes

7.31.0

Features

Fixes

7.30.2

Fixes

7.30.1

Fixes

7.30.0

Features

Fixes

7.29.0

Features

Fixes

7.28.0

Features

Fixes

Performance Improvements

7.27.1

Fixes

7.27.0

Features

Fixes

7.26.0

Features

Fixes

7.25.1

Performance Improvements

7.25.0

Features

Fixes

7.24.1

Fixes

7.24.0

Features

Fixes

7.24.0-beta.0

Features

Fixes

7.23.0

Features

Fixes

7.22.0

Features

Fixes

7.21.0

Features

Fixes

7.20.0

Features

7.19.0

Features

Fixes

7.18.1

Fixes

7.18.0

Features

Fixes

7.17.0

Features

Fixes

7.16.1

Fixes

7.16.0

Features

Fixes

7.15.0

Features

Fixes

7.14.0

7.13.0

If you are using self-hosted Sentry, this version requires Sentry version >= 21.9.0 to work or you have to manually disable sending client reports via the sendClientReports option.

7.12.0

Important notice

This release contains a fix for the sampling of transactions. The SDK applied both sample rates for events and transactions when capturing transactions. Previously, when setting sampleRate to 0.0, the SDK would discard all transactions. This is fixed now by ignoring the sampleRate for transactions. If you use custom values for sampleRate and traceSampleRate or traceSampler, this change will have an impact on you.

If you are using profiling and self-hosted Sentry, this version requires Sentry version >= 22.3.0.

Various fixes & improvements

7.12.0-beta.0

Various fixes & improvements

7.11.0

7.10.2

7.10.1

7.10.0

7.9.0

7.8.0

7.7.0

7.6.1

7.6.0

7.5.4

7.5.3

7.5.2

Various fixes & improvements

7.5.1

7.5.0

7.4.8

7.4.7

7.4.6

7.4.5

7.4.4

7.4.3

7.4.2

7.4.1

7.4.0

7.3.0

7.3.0-beta.0

7.2.10

7.2.9

7.2.8

7.2.7

7.2.6

7.2.5

7.2.4

7.2.3

7.2.2

7.2.1

This release fixes a crucial issue for auto performance instrumentation that caused crashes when using nested ViewControllers.

7.2.0

This release contains support for auto performance instrumentation for ViewControllers, HTTP requests, app start and slow and frozen frames.

Auto Performance Features

More Features

Fixes

Performance Improvements

7.2.0-beta.9

7.2.0-beta.8

7.2.0-beta.7

7.2.0-beta.6

7.2.0-beta.5

7.2.0-beta.4

7.2.0-beta.3

7.2.0-beta.2

7.2.0-beta.1

7.2.0-beta.0

7.1.4

7.1.3

7.1.2

7.1.1

7.1.0

7.0.3

7.0.2

7.0.1

ref: Prefix TracesSampler with Sentry (#1091)

7.0.0

This is a major bump with the Performance Monitoring API and Out of Memory Tracking, many improvements and a few breaking changes. For a detailed explanation how to upgrade please checkout the migration guide.

Breaking Changes

Features

Fixes

7.0.0-beta.1

Features and Fixes

7.0.0-beta.0

7.0.0-alpha.5

Breaking Changes

Features and Fixes

7.0.0-alpha.4

Breaking Changes

Features and Fixes

7.0.0-alpha.3

7.0.0-alpha.2

Features

Breaking Changes

7.0.0-alpha.1

Features and fixes:

Breaking Changes

7.0.0-alpha.0

Breaking Change: 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 on marking frames as inApp docs.

6.2.1

6.2.0

With this version, Sentry groups errors by domain and code. MyDomain 1 and MyDomain 2 are going to be two separate issues in Sentry. If you are using self-hosted Sentry, it requires Sentry version >= v21.2.0 to work. Staying on Sentry < v21.2.0 and upgrading to this version of the SDK won't do any damage. Sentry will group like in previous versions, but you will see a new group because we slightly changed the wording. If you are using sentry.io no action is needed. In case you are not satisfied with this change, you can take a look at SDK fingerprinting to group by domain only.

6.1.4

6.1.3

6.1.2

6.1.1

6.1.0

6.1.0-alpha.1

6.1.0-alpha.0

6.0.12

6.0.11

6.0.10

6.0.9

6.0.8

6.0.7

6.0.6

6.0.5

6.0.4

6.0.3

6.0.2

6.0.1

6.0.0

This is a major bump with lots of internal improvements and a few breaking changes. For a detailed explanation how to updgrade please checkout the migration guide.

Breaking changes:

Features and fixes:

6.0.0-beta.2

Breaking changes:

Fix:

6.0.0-beta.1

This release also enables by default the option attackStacktrace which includes the stacktrace in all events, including captureMessage by default.

Breaking Changes:

Features and fixes:

6.0.0-beta.0

Breaking changes:

Features and fixes:

6.0.0-alpha.0

Breaking Change: This version uses the envelope endpoint. If you are using an on-premise installation it requires Sentry version >= v20.6.0 to work. If you are using sentry.io nothing will change and no action is needed. Furthermore, with this version auto session tracking is enabled per default. This feature is collecting and sending health data about the usage of your application. We are going to add the official migration guide in one of the next beta releases.

Here is an overview of all the breaking changes:

Other new features and fixes:

5.2.2

5.2.1

5.2.0

5.1.10

5.1.10-beta.0

5.1.9

5.1.8

5.1.7

5.1.6

5.1.5

5.1.4

5.1.3

5.1.2

5.1.1

5.1.0

5.0.5

5.0.4

5.0.3

5.0.2

5.0.1

5.0.0

5.0.0-rc.1

5.0.0-beta.7

5.0.0-beta.6

5.0.0-beta.5

5.0.0-beta.4

5.0.0-beta.3

5.0.0-beta.2

5.0.0-beta.1

5.0.0-beta.0

5.0.0-alpha.0

BREAKING: This is the first public release of our new 5.0.0 #339 version of the SDK. The majority of the public API of the SDK changed, now it's more streamlined with other Sentry SDKs and prepared for future updates. Please read the migration guide how to use the new SDK MIGRATION.MD

4.5.0

4.4.3

4.4.2

4.4.1

4.4.0

4.3.4

4.3.3

4.3.2

4.3.1

4.3.0

4.2.1

4.2.0

4.1.3

4.1.2

4.1.1

4.1.0

4.0.1

4.0.0

This should be safe to upgrade from 3.x.x, there are no code changes what so ever. If you are using CocoaPods or Carthage an update should take care of everything, if you were using the source code directly, make sure to remove KSCrash if you were using it.

We recommend updating if you experience any KSCrash related crashes since we fixed bunch of stuff directly in our codebase now.

3.13.1

3.13.0

3.12.4

3.12.3

3.12.2

3.12.1

3.12.0

3.11.1

3.11.0

3.10.0

3.9.1

3.9.0

3.8.5

3.8.4

3.8.3

3.8.2

3.8.1

3.8.0

3.7.1

3.7.0

3.6.1

3.6.0

3.5.0

3.4.3

3.4.2

3.4.1

Fixed messed up Travis build.

3.4.0

Expose sdk property for SentryEvent to allow users to set specific SDK information. -> mainly used in react-native

3.3.3

Remove stripping of __sentry extra because it breaks if the event is serialized more than once.

3.3.2

Fix integrations for sdk context.

3.3.1

Pretty print json request when verbose logging is active.

3.3.0

Change the way extra tags and user is stored.

3.2.1

3.2.0

3.1.3

3.1.2

3.1.1

3.1.0

3.0.11

3.0.10

3.0.9

3.0.8

3.0.7

3.0.6

3.0.5

3.0.4

3.0.3

Bundled KSCrash into Sentry. Note that this is just for Carthage, CocoaPods knows how to link 2 dynamic frameworks together.

3.0.2

3.0.1

3.0.0

This release is a rewrite of the existing codebase, sentry-cocoa now uses Objective-C instead of Swift. Please make sure to check out the docs since this update introduced many breaking changes. https://docs.sentry.io/clients/cocoa/

KSCrash is now optional, you can use Sentry without it, we still recommend using KSCrash by default otherwise Sentry will not catch any crashes.

2.1.11

2.1.10

2.1.9

2.1.8

2.1.7

2.1.6

("app_identifier", bundleID)
("app_name", bundleName)
("app_build", bundleVersion)
("app_version", bundleShortVersion)

2.1.5

2.1.4

2.1.3

2.1.2

2.1.1

2.1.0

SentryClient.shared?.addExtra("key", value: "value")
event.addTag("key", value: "value")

2.0.1

2.0.0 - Rename from SentrySwift to Sentry

1.4.5

1.4.4

1.4.3

1.4.2

1.4.1

1.4.0

Warning

1.3.4

1.3.3

1.3.2

1.3.1

1.3.0

1.2.0

1.1.0

1.0.0

0.5.0 - Remove Apple Crash Report

0.4.1

Fixed for breadcrumbs not always sending on fatal

0.4.0

0.3.3

0.3.2

0.3.1

0.3.0

0.2.1

0.2.0

0.1.0

First pre-release that is ready for testers