Increase in `deadline_exceeded` statuses after upgrade to 5.22.0

[serglom21]

Platform:

• [x] iOS

SDK:

• [x] @sentry/react-native (>= 1.0.0)
• [ ] react-native-sentry (<= 0.43.2)

SDK version: 5.22.0

react-native version: 0.72.3

Are you using Expo?

• [ ] Yes
• [x] No

Are you using sentry.io or on-premise?

• [x] sentry.io (SaaS)
• [ ] on-premise

Configuration:

export const routingInstrumentation = new Sentry.ReactNavigationInstrumentation(
  {
    enableTimeToInitialDisplay: true,
  },
);

Sentry.init({
  environment: 'development'
  sampleRate: 1.0,
  tracesSampleRate: 0.1,
  enableAppHangTracking: false,
  integrations: [
    new Sentry.ReactNativeTracing({
      routingInstrumentation,
      tracePropagationTargets: [currentConfig.DOMAIN],
    }),
  ],
});

---

I have the following issue:

I am seeing some inconsistencies in the data reported and what should be reported based on the SDK behaviour. For example, it is odd to me that some transactions are being marked as 'deadline_exceeded' when they do not exceed the default value for [finalTimeoutMs]. finalTimeoutMs is also not being overridden in the init code block

The default for finalTimeoutMs is 600000ms or 10mins, which is way above what the transactions being marked deadline_exceeded are reporting. The amount of failed transactions with this status seems to have increased after updating the SDK version from 5.3.0 to 5.22.0

More details with links to examples in the Customer Case

[krystofwoldrich]

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.

[lucas-zimerman]

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 in your code

[julianosbentowellhub]

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 in your code

Yep, we are using the Stack.Navigator.

[lucas-zimerman]

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

[julianosbentowellhub]

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?