You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have done an upgrade to eas-cli version 9.0.2 right after the upgrade of expo sdk to version 51.
When I run eas build, I get the error message that the package.json file is missing in ios folder?!
eas build
✔ Select platform › Android
Loaded "env" configuration for the "production" profile: no environment variables specified. Learn more: https://docs.expo.dev/build-reference/variables/
Specified value for "android.package" in app.json is ignored because an android directory was detected in the project.
EAS Build will use the value found in the native code.
✔ Using remote Android credentials (Expo server)
✔ Using Keystore from configuration: Build Credentials 34xVKAd5jG (default)
ConfigError: The expected package.json path: /Users/muellermario/_workingDirectory/_github/TFCH/tfch/ios/package.json does not exist
output from npx expo-doctor:
ConfigError: The expected package.json path: /myproject/ios/package.json does not exist
at getRootPackageJsonPath (/Users/.../.npm/_npx/c15e4b19a90d9797/node_modules/expo-doctor/build/index.js:53:482328)
at getPackageJsonAndPath (/Users/.../.npm/_npx/c15e4b19a90d9797/node_modules/expo-doctor/build/index.js:53:466818)
at getConfig (/Users/.../.npm/_npx/c15e4b19a90d9797/node_modules/expo-doctor/build/index.js:53:465299)
at actionAsync (/Users/.../.npm/_npx/c15e4b19a90d9797/node_modules/expo-doctor/build/index.js:59:100143)
at async run (/Users/.../.npm/_npx/c15e4b19a90d9797/node_modules/expo-doctor/build/index.js:59:101815) {
isConfigError: true,
code: 'MODULE_NOT_FOUND',
cause: undefined
}
Error output
No response
Reproducible demo or steps to reproduce from a blank project
no
The text was updated successfully, but these errors were encountered:
Build/Submit details page URL
No response
Summary
I have done an upgrade to eas-cli version 9.0.2 right after the upgrade of expo sdk to version 51.
When I run eas build, I get the error message that the package.json file is missing in ios folder?!
eas build
✔ Select platform › Android
Loaded "env" configuration for the "production" profile: no environment variables specified. Learn more: https://docs.expo.dev/build-reference/variables/
Specified value for "android.package" in app.json is ignored because an android directory was detected in the project.
EAS Build will use the value found in the native code.
✔ Using remote Android credentials (Expo server)
✔ Using Keystore from configuration: Build Credentials 34xVKAd5jG (default)
ConfigError: The expected package.json path: /Users/muellermario/_workingDirectory/_github/TFCH/tfch/ios/package.json does not exist
Managed or bare?
bare
Environment
output from npx expo-env-info:
expo-env-info 1.2.0 environment info:
System:
OS: macOS 14.4.1
Shell: 5.9 - /bin/zsh
Binaries:
Node: 20.9.0 - /usr/local/bin/node
Yarn: 1.22.19 - /opt/homebrew/bin/yarn
npm: 10.1.0 - /usr/local/bin/npm
Managers:
CocoaPods: 1.14.2 - /opt/homebrew/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 23.4, iOS 17.4, macOS 14.4, tvOS 17.4, visionOS 1.1, watchOS 10.4
IDEs:
Android Studio: 2023.1 AI-231.9392.1.2311.11330709
Xcode: 15.3/15E204a - /usr/bin/xcodebuild
npmGlobalPackages:
eas-cli: 9.0.2
output from npx expo-doctor:
ConfigError: The expected package.json path: /myproject/ios/package.json does not exist
at getRootPackageJsonPath (/Users/.../.npm/_npx/c15e4b19a90d9797/node_modules/expo-doctor/build/index.js:53:482328)
at getPackageJsonAndPath (/Users/.../.npm/_npx/c15e4b19a90d9797/node_modules/expo-doctor/build/index.js:53:466818)
at getConfig (/Users/.../.npm/_npx/c15e4b19a90d9797/node_modules/expo-doctor/build/index.js:53:465299)
at actionAsync (/Users/.../.npm/_npx/c15e4b19a90d9797/node_modules/expo-doctor/build/index.js:59:100143)
at async run (/Users/.../.npm/_npx/c15e4b19a90d9797/node_modules/expo-doctor/build/index.js:59:101815) {
isConfigError: true,
code: 'MODULE_NOT_FOUND',
cause: undefined
}
Error output
No response
Reproducible demo or steps to reproduce from a blank project
no
The text was updated successfully, but these errors were encountered: