stopped receiving transactions on android after migration from 2.4.3 to 2.5.0
See original GitHub issueThis is a follow up issue after https://github.com/getsentry/sentry-react-native/issues/1599
Environment
How do you use Sentry? Sentry SaaS (sentry.io)
Which SDK and version? @sentry/react-native@2.5.0
Steps to Reproduce
- upgrade
@sentry/react-native
from2.4.3
to2.5.0
const transaction = Sentry.startTransaction({ name: 'app.loader' })
const span = transaction.startChild({....})
...
span.finish()
transaction.finish()
Expected Result
being able to see transactions from android
Actual Result
I stopped receiving any transactions from android while ios work well
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:17 (7 by maintainers)
Top Results From Across the Web
Room - Android Developers
Configuring Compiler Options. Room has the following annotation processor options: room.schemaLocation : Configures and enables exporting database schemas into ...
Read more >Issues with Upgrading Spring boot from 2.2.2.Release to 2.4.2 ...
Now we tried to upgrade it to the SpringBoot 2.4.2 version and application is not getting started and throws the following error.
Read more >braintree_android/CHANGELOG.md at master - GitHub
Pass the risk correlation ID from the Native Checkout SDK if it is not provided in the ... Migrate braintree-android-google-payment into braintree_android ...
Read more >Log4j – Changes - Apache Logging Services
Fixes appender concurrency problems in Log4j 1.x bridge. ... The rolling file appenders would fail to compress the file after rollover if ...
Read more >React SDK – Support Help Center
Release notes from Optimizely Full Stack React SDK https://github.com/optimizely/react-sdk/releases.
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 found issues that could cause the transaction not to be sent/received correctly and we’re looking into how we should go about fixing it. Related issues listed below:
getsentry/sentry-java#1541 getsentry/sentry-java#1540 getsentry/sentry-java#1539 getsentry/sentry-java#1538
Looks like the clock drift issue could be back, this could possibly be related. We will need some time to look into this.