Releases: getsentry/sentry-react-native
5.16.0-alpha.4
5.16.0-alpha.3
This release is compatible with expo@50.0.0-preview.6
and newer.
Features
-
withSentryExpoSerializers
changes togetSentryExpoConfig
(#3501)getSentryExpoConfig
accepts the same parameters asgetDefaultConfig
fromexpo/metro-config
and returns Metro configuration- This also works for EAS Updates (and expo export). Debug ID is generated by
expo/metro-config
and used by Sentry.
const { getSentryExpoConfig } = require("@sentry/react-native/metro"); const config = getSentryExpoConfig(config, {});
-
Add
npx sentry-expo-upload-sourcemaps
for simple EAS Update (expo export) source maps upload to Sentry (#3491, #3510)SENTRY_PROJECT=project-slug \ SENTRY_ORG=org-slug \ SENTRY_AUTH_TOKEN=super-secret-token \ npx sentry-expo-upload-sourcemaps dist
-
Sentry CLI binary path in
scripts/expo-upload-sourcemaps.js
is resolved dynamically (#3507)- Or can be overwritten by
SENTRY_CLI_EXECUTABLE
env
- Or can be overwritten by
-
Resolve Default Integrations based on current platform (#3465)
- Native Integrations are only added if Native Module is available
- Web Integrations only for React Native Web builds
-
Remove Native Modules warning from platform where the absence is expected (#3466)
-
Add Expo Context information using Expo Native Modules (#3466)
Fixes
- Includes fixes from version 5.15.2
5.15.2
Fixes
- Stop sending navigation route params for auto-generated transactions, as they may contain PII or other sensitive data (#3487)
- Further details and other strategies to mitigate this issue can be found on our trouble shooting guide page
5.16.0-alpha.2
Features
-
Add
withSentryExpoSerializers
for easy configurablemetro.config.js
(#3454)This Serializer doesn't support EAS Updates (and expo export) commands yet. Debug IDs needed for source maps resolution in Sentry
are generated only during native builds.const { getDefaultConfig } = require('expo/metro-config'); const { withSentryExpoSerializers } = require("@sentry/react-native/metro"); const config = getDefaultConfig(__dirname); module.exports = withSentryExpoSerializers(config);
Note that this will remove any existing
customSerializer
. Guide for advanced setups can be found here.
Fixes
5.15.1
5.16.0-alpha.1
Features
-
Add
@sentry/react-native/expo
Expo config plugin (#3429)This Release introduces the first alpha version of our new SDK for Expo.
At this time, the SDK is considered experimental and things might break and change in future versions.The core of the SDK is Expo plugin which you can easily add to your App config:
const { withSentry } = require('@sentry/react-native/expo'); const config = {...}; module.exports = withSentry(config, { url: 'https://www.sentry.io/', authToken: 'example-token', // Or use SENTRY_AUTH_TOKEN env project: 'project-slug', // Or use SENTRY_PROJECT env organization: 'org-slug', // Or use SENTRY_ORG env });
- And
Sentry.init
inApp.js
import * as Sentry from '@sentry/react-native'; Sentry.init({ dsn: '__DSN__', });
- And
-
Update
sentry-xcode.sh
scripts with Node modules resolution (#3450)- RN SDK and Sentry CLI are dynamically resolved if override is not supplied
Fixes
- Transform shipped JSX for both react-native and web (#3428)
- Removes builds errors when using react-native-web with Webpack
5.15.0
Features
-
New simplified Sentry Metro Serializer export (#3450)
const { createSentryMetroSerializer } = require('@sentry/react-native/metro');
Fixes
- Encode envelopes using Base64, fix array length limit when transferring over Bridge. (#2852)
- This fix requires a rebuild of the native app
- Symbolicate message and non-Error stacktraces locally in debug mode (#3420)
- Remove Sentry SDK frames from rejected promise SyntheticError stack (#3423)
- Fix path from Xcode scripts to Collect Modules (#3451)
Dependencies
5.14.1
5.14.0
Features
- Add iOS profiles to React Native Profiling (#3349)
Fixes
- Conditionally use Set or CountingSet in Sentry Metro plugin (#3409)
- This makes sentryMetroSerializer compatible with Metro 0.66.2 and newer
- Fix SIGSEV, SIGABRT and SIGBUS crashes happening after/around the August Google Play System update, see #2955 for more details