No project ID specified in app.json, unable to sign manifest
See original GitHub issueSummary
Hi,
Just upgraded from SDK 44 to SDK 45.
Everytime I’m launching my app or reloading the JS bundle, I’m having this warning : No project ID specified in app.json, unable to sign manifest

Never had this warning before and I don’t know if this is important or not. I’m also using EAS Updates.
Managed or bare workflow? If you have ios/
or android/
directories in your project, the answer is bare!
managed
What platform(s) does this occur on?
Android, iOS
SDK Version (managed workflow only)
45
Environment
expo-env-info 1.0.3 environment info:
System:
OS: macOS 12.3.1
Shell: 5.8 - /bin/zsh
Binaries:
Node: 16.13.1 - ~/.nvm/versions/node/v16.13.1/bin/node
npm: 8.3.0 - ~/.nvm/versions/node/v16.13.1/bin/npm
Managers:
CocoaPods: 1.11.2 - /Users/yonitouboul/.rbenv/shims/pod
SDKs:
iOS SDK:
Platforms: DriverKit 21.4, iOS 15.4, macOS 12.3, tvOS 15.4, watchOS 8.5
IDEs:
Android Studio: 2020.3 AI-203.7717.56.2031.7935034
Xcode: 13.3.1/13E500a - /usr/bin/xcodebuild
npmPackages:
babel-preset-expo: ~9.1.0 => 9.1.0
expo: ^45.0.0 => 45.0.0
react: 17.0.2 => 17.0.2
react-dom: 17.0.2 => 17.0.2
react-native: 0.68.1 => 0.68.1
npmGlobalPackages:
eas-cli: 0.52.0
expo-cli: 5.4.3
Expo Workflow: managed
Reproducible demo
Upgrade from 44 to 45 and run expo start
Issue Analytics
- State:
- Created a year ago
- Reactions:2
- Comments:10 (1 by maintainers)
Top Results From Across the Web
app.json / app.config.js - Expo Documentation
The Expo sdkVersion to run the project on. This should line up with the version specified in your package.json. runtimeVersion. Type: undefined.
Read more >Problem validating app.json: Unable to perform cache refresh
Problem got fixed for me after updating the expo-cli to the latest version: npm install -g expo-cli.
Read more >Manual: Setting up your project for Unity services
You can create a new Project ID within the Unity Editor, or in the Unity developer dashboard. To link your project from the...
Read more >Web Application Manifest - W3C
This specification defines a JSON-based file format that provides developers with a centralized place to put metadata associated with a web ...
Read more >Web app manifests - MDN Web Docs - Mozilla
Chrome Edge
display Full support. Chrome39. Toggle history Full support. Edge7...
display_override. Experimental Full support. Chrome89. Toggle history Full support. Edge8...
icons Full support. Chrome39. Toggle...
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
I encountered this issue also. We upgraded to Expo 45 so I ran the command
eas update:configure
to configure updates as we had been previously usingexpo publish
for OTA updates. Expo 45 does not support updates for free tier right now, but it will be available later in 2022 according to the Expo 45 release notes.From the link:
Later this year, we’ll release EAS Update to all accounts, allow secure end-to-end code signing, and much more. Stay tuned!
I fixed the issue by removing the changes that the command
eas update:configure
had made to the app.json file. I removed the “updates” and “runtimeVersion” sections in the app.json. I also uninstalled theexpo-updates
package as it is of no use until it is made available to the free tier.I hope this helps someone else. It is frustrating that Expo had previously made
expo publish
commands available to all users but now the updates are only available to paid accounts until later this year. We used the OTA updates quite alot to deploy different versions to testers and also for patches to production versions of our app.https://github.com/expo/expo/issues/17693#issuecomment-1168147226