87
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 Feed
Sort by
J
Justin Martinez
Is there any work planned to be able to delete channels?
J
Justin Martinez
actually, it looks like there is an undocumented
eas channel:delete
command availableMark Han
"Release channels are currently visible in the web UI, and through the EAS CLI." I can't find them anywhere.
Right now I can't find any way to easily get to Release Channels from the Web UI. Also, I know that expo publish will soon be deprecated, but it would be great if the
default
channel could be changed. And if we do have other release channels that we expo publish to, it would be nice to be able to see those channels in the Expo Go app, because currently it only shows the default channel and "recently opened" channels, which don't seem to last long.One last thing: It would be really nice to be able to expo publish a dev (debuggable) version of our app.
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
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.
Load More
→