-
-
Notifications
You must be signed in to change notification settings - Fork 354
Closed
Description
OS:
- Windows
- MacOS
- Linux
Platform:
- iOS
- Android
SDK:
-
@sentry/react-native(>= 1.0.0) -
react-native-sentry(<= 0.43.2)
SDK version: v4.3.1
react-native version: 0.66.4
Are you using Expo?
- Yes
- No
Are you using sentry.io or on-premise?
- sentry.io (SaaS)
- on-premise
If you are using sentry.io, please post a link to your issue so we can take a look:
[Link to issue]
Configuration:
(@sentry/react-native)
// In the App's componentDidMount
SentrySdk.init({
dsn: sentryConfig.dsn,
release: releaseIdentifier,
dist: BuildInfo.buildVersion,
enableAutoSessionTracking: true,
enableAutoPerformanceTracking: true,
tracesSampleRate: 0.1,
integrations: [
new SentrySdk.ReactNativeTracing({
// Pass the React Navigation instrumentation to be used as `routingInstrumentation`
// See https://docs.sentry.io/platforms/react-native/performance/instrumentation/automatic-instrumentation/#react-navigation-v4
routingInstrumentation,
}),
],
});
I have following issue:
We track the performances of our React Native app.
Actual result:
The cold startup time is given at ~2 seconds, which is okay...
The warm startup time is given at 24h.
Expected result:
The warm startup time should be accurate, around a few ms or seconds.
Is this a known bug? Or have we missed something in our configuration?
Metadata
Metadata
Assignees
Labels
No labels
Projects
Status
Done