Sentry Empower Plant React Native (Expo) Demo

This is a demo repo used by Solution Engineers when demo'ing Sentry's React Native SDK's capabilities. This version is built with Expo (SDK 57).

Home Screen	Product Detail	Cart

Versions

See package.json for up to date information about the @sentry/react-native SDK, react-native, and expo versions.

Setup

1. git clone git@github.com:sentry-demos/sentry_react_native.git
2. Optional — Add your DSN and BACKEND_URL to src/config.ts
3. Optional — Create .env.local in project root and add EXPO_PUBLIC_SE=<value>
4. export SENTRY_AUTH_TOKEN=<token> — How to generate a Sentry Auth Token
5. npm install

Development

This app uses native modules (the Sentry config plugin), so it can't run in Expo Go — npm run android / npm run ios generate the native projects and build a dev client.

# Start the Metro dev server against an already-installed dev build
npm start

# Generate the native project and build/install it
npm run android
npm run ios

For release builds, the same flow CI uses (see .github/workflows/build-*.yml):

npx expo prebuild --platform android
cd android && ./gradlew :app:assembleRelease

The generated android/ and ios/ directories are gitignored — expo prebuild recreates them from app.config.js, so don't edit them by hand.

Releases

Releases are automated via .github/workflows/release.yml and use date-based versioning, matching the sentry-demos/android demo: version name YY.M.D (e.g. 26.10.5) and version code YYMMDD (e.g. 261005).

• Scheduled: every Monday at 00:00 UTC. The workflow bumps package.json, builds the Android APK and iOS app, and publishes them to GitHub Releases as app-release.apk and sentry_react_native.app.zip. The TDA pipeline always tests against the latest release, so its errors are tagged with the current version.
• Manual: Actions → Release → Run workflow, no inputs needed. It releases with today's date just like the scheduled run. If today was already released, the version gets a suffix (26.10.5-1, then -2, …) so it never collides with the automated releases.

The version input on the workflow is an optional escape hatch for forcing a specific version; it fails if that version was already released.

Environment Variables

Expo reads .env.local automatically. Variables must be prefixed with EXPO_PUBLIC_ to be accessible in app code:

EXPO_PUBLIC_SE=tda

This replaces the react-native-dotenv / @env approach from the bare RN version.

Differences from the bare React Native version

Area	Bare RN	Expo
Icons	react-native-vector-icons	@expo/vector-icons (built-in)
Env vars	import {SE} from '@env'	process.env.EXPO_PUBLIC_SE
Metro config	withSentryConfig	getSentryExpoConfig
Build	react-native run-*	expo prebuild + expo run:*
Sentry plugin	Android Gradle plugin	Expo config plugin (@sentry/react-native)

Troubleshooting

See troubleshooting.md for tips.