Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Error: Unable to resolve module `react-native/Libraries/promiseRejectionTrackingOptions`
See original GitHub issuereact native：0.61.4 sentry：3.2.4
error: bundling failed: Error: Unable to resolve module react-native/Libraries/promiseRejectionTrackingOptions from node_modules/@sentry/react-native/dist/js/integrations/reactnativeerrorhandlers.js: react-native/Libraries/promiseRejectionTrackingOptions could not be found within the project.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:16 (7 by maintainers)
Top Results From Across the Web
Error: Unable to resolve module process · Issue #63 · tradle ...
I am using react native 0.66 and after I import the shim file and run the app I get this error error: Error:...
Read more >Unable to Resolve Module in React Native App
I'm getting an error in React Native saying it can't resolve a module. It's saying a certain folder doesn't exist but the path...
Read more >MongoDB Atlas App Services & Realm
Fresh Setup: Realm React Native Error: Unable to resolve module `./subscription` from `node_modules/realm/lib/browser/index.js`.
Read more >Running bundle using React Native and Javascript SDK ...
Running bundle using React Native and Javascript SDK causes an error. Bundling failed: Error: Unable to resolve module `util`.
Read more >React Native, Typescript and VS Code: Unable to resolve ...
The problem with resolving modules turned out to be related to VS Code's typescript project helper.
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 Free
Top 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
@marandaneto Yes, it is a runtime error.
I’ve added:
but it didnt work.
@jennmueng The error has been fixed，i am using version 3.2.5.
https://github.com/getsentry/sentry-react-native/releases/tag/3.2.5 fixes the issue, thank you all for the logs and sorry for the inconvenience. gonna work on https://github.com/getsentry/sentry-react-native/issues/1924 soon to avoid such issues and detect them earlier.