No errors reported since upgrading to 3.0.1 from 2.6.2
See original GitHub issueEnvironment
How do you use Sentry?
- Sentry SaaS (sentry.io)
Which SDK and version?
- sentry-expo:
^4.0.1
- @sentry/react-native:
^3.1.0
Steps to Reproduce
- Upgrade
@sentry/react-native
from2.6.2
to3.0.1
- Use the app as usual
- Notice that after a week or so, no issues have been reported (even after manually triggering an error)
Expected Result
I’d expect to see any errors in Sentry but there’s been nothing reported since just before upgrading to 3.0.1
.
Actual Result
No errors in Sentry.
Extra information
My app started as a managed Expo app and a while ago I ejected to the bare workflow. Since then, I’ve been using @sentry/react-native
and sentry-expo
as shown here in Expo’s docs.
Setup
sentry.ts
import { Platform } from 'react-native'
const SENTRY_DSN_IOS = '...'
const SENTRY_DSN_ANDROID = '...'
export const sentryConfig = {
dsn: Platform.OS === 'ios' ? SENTRY_DSN_IOS : SENTRY_DSN_ANDROID,
enableInExpoDevelopment: true,
enableAutoSessionTracking: true,
debug: __DEV__ ? true : false,
environment: __DEV__ ? 'development' : 'production',
}
App.tsx
import * as Sentry from 'sentry-expo'
import { sentryConfig } from './config/sentry'
// ...
Sentry.init(sentryConfig)
// ...
Sentry.Native.captureException(error) // Example error after unsuccessful API call, etc.
This setup has been working for quite some time, despite issues with source maps mentioned in #1350.
What am I missing? Was I supposed to do some extra configuration when updating to 3.0.1
? If there’s any further information that I could send that may help, just let me know.
Thanks for your time! Have a nice day.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:14 (4 by maintainers)
Top Results From Across the Web
CocoaPods Fails On Apple Silicon | Apple Developer Forums
Hi, I was trying to build my app on Apple Silicon on a DTK, but it fails, because the RubyGems is having some...
Read more >cannot install the best update candidate for package
using Red Hat Enterprise Linux release 8.4 (Ootpa). ran into these 5 problems while updating. sudo yum update
Read more >Plugin 'org.springframework.boot:spring-boot-maven-plugin ...
I fixed the problem adding the version of the plugin in the pom.xml, which is the same of spring boot's version. (and it's...
Read more >Upgrade Guide and API Changes - Apache Kafka
Upgrading from any versions as old as 0.10.0.x to 3.0.0 in offline mode require the ... Since 2.6.0 release, Kafka Streams depends on...
Read more >Preparing for Spring Boot 3.0
Spring Boot 3.0 will require Java 17, but you don't need to wait until that release to upgrade to the latest LTS Java...
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
Hi guys, I’m not using Expo at all, just react-native, and by upgrading from
2.1.0
to3.0.1
I’m having the same issues. Error reporting just stopped working in production mode, but works fine in dev mode.I was able to identify the problem, it’s down to codepush & sentry wrapper order.
Before (doesn’t work) :
After (working) :
Not sure why though 😔
Hi, @jennmueng.
Since
sentry-expo
was just updated to use"@sentry/react-native": "^3.1.1"
, I’m now seeing errors again in Sentry. Note that I’m still using thesentry-expo
import as I was prior to the issue starting when the version mismatch happened. Thank you so much for your continued support — it’s very much appreciated.