78
See all release channels (and delete them?) from expo site/app
in progress
Alex Russell
When I'm viewing my experience's project page (as the owner), it'd be useful to see all release channels that exist, get the QR for that specific experience and maybe even delete any that should no longer exist.
Same goes for the expo app - I should be able to load up any "version" of my app if multiple channels exist.
Kim Brandwijk
in progress
Release channels are currently visible in the web UI, and through the EAS CLI. The upcoming version of Expo Go and Development Client will also include functionality for this in the apps.
Activity
Newest
Oldest
Kim Brandwijk
Kim Brandwijk
in progress
Release channels are currently visible in the web UI, and through the EAS CLI. The upcoming version of Expo Go and Development Client will also include functionality for this in the apps.
Guille Acosta
I think this is absolute necessary. It would take expo go app to the next level.
Matt Carroll
If an app does not have a "default" release channel, the app cannot be opened from the Expo Client without going to the correct URL (the release-channel querystring parameter does not seem to be documented anywhere, we only found it by chance).
This is making it very difficult for us to share our app for testing as we want to save the default environment for when we go live which won't be until we have done sufficient user testing on a UAT environment.
Matt Carroll
Brent Vatne
I like this idea! We will absolutely consider it
J
Jakub Freywald
Brent Vatne: Hey, any news on this one? We just started using expo, and since we need to keep specific versions of our app separate & available for download for QA, owners etc., this would be a killer feature to have! (Kind of a necessity at this point, really...)
Brent Vatne
Jakub Freywald: this does not exist yet, but you can share the url to the website with your team to open the project on the target release channel. when you publish you will be given a project page url such as https://expo.io/@jakub/myapp?releaseChannel=some-channel -- that is the url to share. they can then scan that qr code and open the app
K
KendallRoth
Brent Vatne: Just checking in on this again, any update on this or is it still at the same stage as before?
Brent Vatne
KendallRoth: we're working on something similar for an upcoming new service called EAS Update, along with expo-dev-client: https://docs.expo.dev/clients/introduction/
we're not working on this for expo go
Matt Carroll
If an app does not have a "default" release channel, the app cannot be opened from the Expo Client without going correct URL (the release-channel querystring parameter does not seem to be documented anywhere, we only found it by chance).
This is making it very difficult for us to share our app for testing as we want to save the default environment for when we go live which won't be until we have done sufficient user testing on a UAT environment.
Brian Sykes
Agree. Would love to see a list of release channels from the site, as well as a Channels section in the app.
Eric James
Deleting release channels (essentially bricking users) is useful for me because:
- I want to 100% offload users using deprecated API endpoints
- Some release channels were beta test versions not meant to "exist" anymore
- Sanity for other developers to know what is being used and what isn't
At minimum, if we can at least SEE all the release channels associated with a project, I can push updates to those users. Yes I know this is sort of on the developer's part to keep track of old releases, but developers change, companies change, and deprecated stuff may not get followed up. I imagine the difficulty of maintaining all the Expo SDK versions, we too are in the same bind!
Petr Peller
Would be nice to be able to delete a release channel or deploy to a temporary channel that will be deleted automatically after X days.
We currently have 1 release channel per feature branch that is deployed to using CI. I am worried that eventually Expo servers will get full :)
Load More
→