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
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.
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 .
The text was updated successfully, but these errors were encountered: