All transactions are marked as deadline_exceeded
See original GitHub issueOS:
- Windows
- MacOS
- Linux
Platform:
- iOS
- Android
SDK:
-
@sentry/react-native
(>= 1.0.0) -
react-native-sentry
(<= 0.43.2)
SDK version: 4.3.0
react-native
version: 0.67.2
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 transaction so we can take a look:
Configuration:
(@sentry/react-native
)
const sentryRoutingInstrumentation = new Sentry.ReactNavigationInstrumentation();
Sentry.init({
dsn: '...'
environment: 'production',
integrations: [
new Sentry.ReactNativeTracing({
tracingOrigins: [
/^.*images\.goproperly\.com.*/,
/^.*\.amazonaws\.com.*/,
/^.*\.algolia.net.*/,
],
routingInstrumentation: sentryRoutingInstrumentation,
}),
],
tracesSampleRate: 1,
// Send analytics to Segment when we get a crash or error
beforeSend(event) {
const { level, message, exception } = event;
let errorMessage = message ?? '';
if (exception?.values?.length) {
if (errorMessage.length) {
errorMessage += ' ';
}
errorMessage += exception.values.map((v) => v.value).join(' ');
}
if (level === 'fatal' || level === 'error') {
segmentClient.track('Application Crashed', {
message: errorMessage,
level,
});
}
return event;
},
});
I have following issue:
All the transactions reported by react-native Sentry SDK v4.3.0 are marked as deadline_exceeded
.
I’ve tried setting ReactNavigationInstrumentation.routeChangeTimeoutMs
or ReactNativeTracing.idleTimeout
to 10,000ms but nothing changed.
!transaction.status:deadline_exceeded
transaction.status:deadline_exceeded
example of a transaction
Issue Analytics
- State:
- Created a year ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
sql: TransactionStatusError: transaction deadline exceeded ...
When running TPCC with more than a single thread, occasionally a transaction will fail with the following error: pq: TransactionStatusError: ...
Read more >Troubleshoot Cloud Spanner deadline exceeded errors
This page provides an overview of Cloud Spanner deadline exceeded errors: what they are, ... Spanner transactions need to acquire locks to commit....
Read more >503 errors thrown due to Gitaly Deadlines Exceeded - GitLab
Summary A lot of calls come back with 503, the log always seems to refer to Gitaly Dealines being exceeded.
Read more >Firebase cloud function: error in running transactions
I get the error message: 'Error: 4 DEADLINE_EXCEEDED: Deadline exceeded'; All the documents in the 'comments' collection are deleted ...
Read more >failed to create new connection context deadline exceeded ...
I am practising the Build your first network tutorial. When I run ./byfn.sh up, I get ... connection context deadline exceeded.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
We currently don’t set any status in RN, so
unknown
is expected.@marandaneto Setting
maxTransactionDuration: 600 * 1000
gives me the statusunknown
. I’m not sure if that’s intended.See transaction here.