Hi @serglom21,
thank you for the message,

I agree, it doesn't sound right, that these transaction are marked as deadline_exceeded. I'll take a look at the examples and keep you updated.

Are you using something on the screens with deadline_exceeded a code called Stack.Navigator to switch between different pages? You can usually find it by looking for the term <Stack.Navigator> in your code

Are you using something on the screens with deadline_exceeded a code called Stack.Navigator to switch between different pages? You can usually find it by looking for the term <Stack.Navigator> in your code

Yep, we are using the Stack.Navigator.

Hi, I found a potential fix for your case and a solution will be implemented soon on the SDK.

Hi, I found a potential fix for your case and a solution will be implemented soon on the SDK.

@lucas-zimerman thanks a lot for it, we are expecting to solve this issue ASAP to normalize our failure_rate metrics. When you had an stable version with the fix, could you share it here, pls?

@julianosbentowellhub definitely, we'll update here when the fix is verified and released.

@kahest same issue here: deadline_exceeded on all route change using react native Stack.Navigator.

Here is our configuration:

Sentry.init({
  dsn: '...',
  debug: true,
  environment: ENV.APP_ENV,
  tracesSampleRate: 1,
  enableNative: true,
  sampleRate: 1,
  attachStacktrace: true,
  ignoreErrors: [
    /.*[Network error]: Error: Socket closed.*/i,
    /.*Socket closed.*/i
  ],
  _experiments: {
    profilesSampleRate: 1
  },
  enableAutoPerformanceTracing: true,
  integrations: [
    new Sentry.ReactNativeTracing({
      enableUserInteractionTracing: true,
      enableStallTracking: true,
      enableHTTPTimings: true,
      enableAppStartTracking: true,
      maxTransactionDuration: 600 * 1000,
      enableNativeFramesTracking: true,
      routingInstrumentation: {  
          enableTimeToInitialDisplay: true,
          routeChangeTimeoutMs: 6000  
       }
    })
  ]
});

Hi @jimmysafe,
thank you for the message,

are there any specific span in the transactions, which are causing the deadline_exceeded? For example the Time To Display spans?

Hi @krystofwoldrich

The span which hangs and fails is the navigation span, i guess the issue is related to the fact we are using the <Stack.Navigator> in react native.

Also the Time to inital display is affected too by being always cancelled.

Please let me know if you need more info :)

@jimmysafe Thank you for the confirmation,

• this will be fixed by Fix: Implement fallback system to screens that aren't reporting on the native layer the time to display. #4042

At the moment you can use manual TTID APIs https://docs.sentry.io/platforms/react-native/tracing/instrumentation/time-to-display/#time-to-initial-display-overwrite as a workaround or temporarly disable the feature.

Hi @sregg,
thank for the message,

are you experiencing this on iOS or Android?

Note I saw iOS in #3786

Are you able to reproduce it locally? Would you be able to share a reproducible example?

iOS and Android.
It's mostly in the wild from now but I can try to repro locally.
I believe last time I was seeing that when I would navigate back to the screen.
I'll report back.

Also, is it normal that the status is unknown when it's not timing out?

Here's our home screen for example:

I'm able to repro the deadline_exceeded and the 15s timeout every time I navigate back to a screen

@sregg same here, we get tons of unknown status and i can confirm that even by using the <Sentry.TimeToInitialDisplay record={true} /> the issue of of deadline_exceeded persists.

Thank you both for the reports, we're working on this. Which versions of the SDK are you using?

Thank you both for the reports, we're working on this. Which versions of the SDK are you using?

v5.31.1