Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can we publish directly to the "production" environment of the app stores? #1245

Closed
simoneb opened this issue Jul 28, 2023 · 1 comment · Fixed by #1248
Closed

Can we publish directly to the "production" environment of the app stores? #1245

simoneb opened this issue Jul 28, 2023 · 1 comment · Fixed by #1248
Assignees
Labels

Comments

@simoneb
Copy link
Member

simoneb commented Jul 28, 2023

This application is being automatically published to the stores via eas submit when there is a release made with Optic, as usual.

The problem is that it goes to a "channel", both in the Apple and Play stores, that is for internal testing and requires manual steps to take to production. Those manual steps furthermore require that somebody logs into the stores websites, which few people have access to.

We would like to see if it's possible, given the nature of the application, to skip this step altogether and, when a new release is made in the repo, publish the store apps directly to production.

Relevant docs exist on the Expo website: https://docs.expo.dev/submit/introduction/. Everything else can be found in this repository, such as the eas configuration file, and the files where the expo commands are executed are the yaml workflow files.

People with some level of knowledge on this topic that you may want to reach out to are @confraria and @manosim .

@github-actions
Copy link

github-actions bot commented Aug 4, 2023

🎉 This issue has been resolved in version 1.4.4 🎉

The release is available on:

Your optic bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants