Boom, let the project download/build and the next screen you should see is this:
XDE does a great job of handling a lot of the building errors, dependencies and stuff you don’t want to mess with, and gives you very helpful messages when it can’t fix it on it’s own.
Some of those issues and learnings that I have came across when I upgrading from Expo’s SDK 22.0 to SDK 25.0 were as follows:
npm startto start the project, all was good, but when I upgraded to SDK 25.0,
npm startno longer works, it’s
yarn startnow. I realize that is probably a derp on my part, but still thought I should mention it.
"sdkVersion": "25.0.0",, if it’s lower, look into updating your node version, that is what is blocking you from not being able to use the newest Expo SDK.
That literally is it, you have a working blank native app running on your machine!
These next screenshots below are showing the app project options available with XDE. That refresh (clear cache) button will be your friend as you are installing new packages and trying new file structures as you are building your new app, so keep that in mind please! Sometimes the errors that are being causes is just from old cached file/directory structures.
No coding today, just an overview, but… your homework is: find and use the XDE share button to view the running app’s QR code and get that blank app running on your physical iPhone or Android device… go!
Go to my next blog post… React Native Project Folder Structure