-
-
Notifications
You must be signed in to change notification settings - Fork 353
Closed
Description
As far as I know, this is how the configuration of the Sentry client needs to happen on a ReactNative application:
- DSN (and others) need to be in the
ios/sentry.properties
andandroid/sentry.properties
files - The DSN needs to be accessible within the JavaScript in order to call
Sentry.config(DSN).install()
. We are using react-native-config, which is populating theDSN
variable from either a.env
file (or from the plist file for instance).
The thing is: we'd love to be able to identify that some errors are coming from the "staging" or others from the "production" application. What's the best way to handle this?
Note that I'm happy that this might be a non-issue if we believe that the application builds should "simply" be promoted from staging to production without any rebuild. Even though it makes little sense as we definitely need different API URLs, etc...
Metadata
Metadata
Assignees
Labels
No labels