I get this error when making an attempt to make my software dwell with Expo Software Service (EAS). However building continues. I initialized my software with expo naked workflow.
Operating “expo physician”
Operating 10 checks in your challenge…
✔ Test Expo config for frequent points
✔ Test bundle.json for frequent points
✖ Test dependencies for packages that shouldn’t be put in immediately
✖ Test for frequent challenge setup points
✔ Test Expo config (app.json/ app.config.js) schema
✔ Test npm/ yarn variations
✖ Test that packages match variations required by put in Expo SDK
✔ Test for legacy world CLI put in regionally
✔ Test that native modules don’t use incompatible assist packages
✔ Test that native modules use suitable assist bundle variations for put in Expo SDK
Detailed examine outcomes:
Recommendation: Use ‘npx expo set up –check’ to evaluate and improve your dependencies.
Some dependencies are incompatible with the put in expo model:
[email protected] – anticipated model: 0.69.9
Your challenge could not work appropriately till you put in the right variations of the packages.
Set up particular person packages by operating npx expo set up [email protected]
Discovered outdated dependencies
The bundle “expo-modules-core” shouldn’t be put in immediately in your challenge. It’s a dependency of different Expo packages, which can set up it mechanically as wanted.
This challenge has native challenge folders however can be configured to make use of Prebuild. EAS Construct won’t sync your native configuration if the ios or android folders are current. Add these folders to your .gitignore file in case you intend to make use of prebuild (aka “managed” workflow).
This challenge has a number of bundle supervisor lock recordsdata (yarn.lock, package-lock.json). This will likely trigger EAS construct to revive dependencies with a special bundle supervisor from what you employ in different environments.
A number of checks failed, indicating attainable points with the challenge.
Command “expo physician” failed.
npx -y expo-doctor exited with non-zero code: 1