"The Expo SDK requires Expo to run" red screen
See original GitHub issueDoes this module only work with Expo apps, or apps that were once on Expo, but subsequently ejected?
I ask because I’m trying to use the module against an app that has never been on Expo, and it’s red screening with the following error:
The Expo SDK requires Expo to run. It appears the native Expo modules are unavailable and this code is not running on Expo
I’ve added Expo as dependency, yarn add expo
. Is there something else that I need to do?
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:8 (3 by maintainers)
Top Results From Across the Web
"The Expo SDK requires Expo to run" red screen since install 2.2.1 ...
Red screen: The Expo SDK requires Expo to run. It appears the native Expo modules are unavailable and this code is not running...
Read more >The expo sdk requires expo to run. it appears the native expo ...
I am getting a red screen with the error "the expo SDK requires expo to run. it appears the native expo modules are...
Read more >Notifications - Expo Documentation
Allows applications to use exact alarm APIs. iOS. No usage description required, see notification-related permissions.
Read more >The Expo SDK requires Expo to run. i am beginner in react ...
Coding example for the question The Expo SDK requires Expo to run. i am beginner in react-native?-React Native.
Read more >Expo SDK 40 is now available - DEV Community
Run expo upgrade in your project directory (requires the latest version of expo-cli, you can update with npm i -g expo-cli ). If...
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
@RishabhTayal,
Only the one that I described in my last post, which was to use @wcandillon 's React Native Image Cache instead.
That’s a short term solution only though: the project is not maintained. So I will be looking into this issue again soon, and I’ll post any advances that I make here. I may end up just creating an empty Expo project, ejecting it and then copying over my source code.
In my case, this problem occurred because of inconsistent versions of Nodejs and NPM… I downgraded the npm version and the problem solved. I use Node 8.11.3 and should use npm version 5.6.0 but I used npm 6.4.1 . I downgraded the npm version to 5.6.0 by npm install -g npm@5.6.0 and the problem solved… You can see compatible versions of npm and Node at the link below: Node and NPM version
I hope that this solution will also be useful to others…