currently not support expo 44
See original GitHub issuejust follow the quick start
npx create-react-native-app -t with-three
start app with ios simulator
error just came up from start
but expo web is working perfectly
anyone can help with this?
package.json
{
"dependencies": {
"expo": "^44.0.0",
"expo-gl": "~11.1.1",
"expo-three": "~5.7.0",
"react": "17.0.1",
"react-dom": "17.0.1",
"react-native": "0.64.3",
"react-native-web": "0.17.1",
"three": "^0.122.0"
},
"devDependencies": {
"@babel/core": "^7.12.9"
}
}
Issue Analytics
- State:
- Created 2 years ago
- Reactions:9
- Comments:13
Top Results From Across the Web
Expo SDK 44. Today we're announcing the release of…
Hermes warnings now have built-in support and show a much more helpful snippet. Added the new expo run:ios --no-build-cache flag for cleaning the...
Read more >react native - getting error after upgrading to expo sdk 44 to 46
Invariant Violation: "main" has not been registered. This can happen if: * Metro (the local dev server) is run from the wrong folder....
Read more >Expo - Twitter
Designed for speed #️⃣ Supports blurhash Disk cache Empowered by. @Expo ... react-native-fast-image is no longer maintained, so even more powerful ...
Read more >expo-updates - npm
Note: expo eject (mentioned @9:10) is no longer needed to implement native code. ... In expo-updates@0.9.0 and above, we support automatic ...
Read more >Unboxing Expo SDK 44 - YouTube
Introduction to EAS Update: https://bit.ly/eas-update-unboxingExpo SDK 44 announcement: https://bit.ly/sdk- 44 -unboxingSource code of the ...
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
@NikitaDudin Yeah, it’s actually worked. @kennedy0527 Just paste
to your package.json to avoid using dirty way playing with SDK versions More about
resolutions
: https://classic.yarnpkg.com/lang/en/docs/selective-version-resolutions/ npm alternative: https://docs.npmjs.com/cli/v8/configuring-npm/package-json#overridessure