v0.32.1

• Update sentry-wizard

v0.32.0

Breaking changes

Migration guide upgrading from < 0.32.0

Since we now use @sentry/wizard for linking with out new @sentry/cli package, the old
sentry-cli-bin package has been deprecated.
You have to search your codebase for sentry-cli-binary and replace it with @sentry/cli.
There are few places where we put it during the link process:

• In both sentry.properties files in ios/android folder
• In your Xcode build scripts once in Bundle React Native code and images and once in Upload Debug Symbols to Sentry

So e.g.:

The Upload Debug Symbols to Sentry build script looks like this:

export SENTRY_PROPERTIES=sentry.properties
../node_modules/sentry-cli-binary/bin/sentry-cli upload-dsym

should be changed to this:

export SENTRY_PROPERTIES=sentry.properties
../node_modules/@sentry/cli/bin/sentry-cli upload-dsym

General

• Bump @sentry/wizard to 0.7.3
• Bump sentry-cocoa to 3.10.0
• Fixed #169

v0.31.0

• Use https://github.com/getsentry/sentry-wizard for setup process

v0.30.3

• Fix podspec file
• Fix gradle regex to allow number in projectname

v0.30.2

Updated npm dependencies

v0.30.1

Deploy and release over Probot

v0.30.0

Refactored iOS to use shared component from sentry-cocoa.
Also squashed many little bugs on iOS.

• Fixed #281
• Fixed #280

v0.29.0

• Fixed #275
• Fixed #274
• Fixed #272
• Fixed #253

v0.28.0

We had to rename project.ext.sentry to project.ext.sentryCli because our own proguard gradle plugin was conflicting with the name.
The docs already reflect this change.
#257

We now use the mainThread to report errors to RNSentry. This change is necessary in order for react-native to export constants.
This change shouldn't impact anyone using react-native-sentry since most of the "heavy" load was handled by sentry-cocoa in its own background queue anyway.
#259 #244

Bump sentry-cocoa to 3.8.3

v0.27.0

We decided to deactivate stack trace merging by default on iOS since it seems to unstable right now.
To activate it set:

Sentry.config("___DSN___", {
      deactivateStacktraceMerging: false
});

We are looking into ways making this more stable and plan to re-enable it again in the future.