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.
Expo SDK 36 Error due to react-native-netinfo
See original GitHub issueHi,
I just upgraded my expo app to sdk 36 and I’m getting an error with react-native-netinfo import. I believe this can be related to this expo/expo#4764
Issue Analytics
- State:
- Created 4 years ago
- Reactions:6
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Developers - Expo SDK 36 Error due to react-native-netinfo -
Hi,. I just upgraded my expo app to sdk 36 and I'm getting an error with react-native-netinfo import. I believe this can be...
Read more >NetInfo has been removed from React Native - Stack Overflow
My project is a React Native app using Expo. Recently, when I was adding some packages to get testing working, I started to...
Read more >"React Native version mismatch" errors - Expo Documentation
This can happen after upgrading your React Native or Expo SDK version, or when connecting to the wrong local development server.
Read more >expo sdk 43
Expo Sdk 43expo install @react-native-community/netinfo expo install ... 0 I get this error running on android emulator "36.
Read more >unable to resolve module @react-native-community/netinfo
I'm try to run expo project on iOS. When I run command expo start , Metro bundle starts successfully but when I click...
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
@vikrantnegi @rafamrs
Thanks for the report. We’re working on testing the fix and aim to have a release out by Monday.
I also got this, and this is definitely related with https://github.com/expo/expo/issues/4764. I disabled bugsnag temporarily