Edit this page
An introduction to automate and maintain your app store presence from the command line with EAS Metadata.
EAS Metadata is in beta and subject to breaking changes.
EAS Metadata enables you to automate and maintain your app store presence from the command line.
You need to provide a lot of information to multiple app stores before your users can use your app. This information is often about complex topics that don't apply to your app. You have to start a lengthy review process after providing the information. When the reviewer finds any issues in the information you provided, you need to restart this process.
EAS Metadata uses a store.config.json file to provide information instead of going through multiple forms in the app store dashboards. When it's time to update the app stores, you can push the store config to the app stores.
- eas metadata:pushEAS Metadata can also instantly identify known app store restrictions that could trigger a rejection after a lengthy review queue.
Adding the store config file to your repository enables you to collaborate with other team members to prepare the app submission.
Using VS Code? Install the Expo Tools extension for auto-complete, suggestions, and warnings in your store.config.json files.
Add EAS Metadata to a new project, or generate the store config from an existing app.
Customize the store config to adapt EAS Metadata to your preferred workflow.
Explore all configurable options EAS Metadata has to offer.