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
Is your feature request related to a problem? Please describe.
We use a pattern of development where we have infrequent builds but frequent updates. We ship a new build when the native code in our dev client changes. Then, whenever a PR is opened we create a channel and ship an update on that channel. Then, we use the dev client build build to load those updates. This lets us QA our code changes without the time sink of native app builds.
Describe the solution you'd like
Ideally expo-orbit://u.expo.dev/[project ID]?channel-name=pr-875 would open a dev client in the simulator and load the update. Likely, we'd need to specific the build to use as well, but I'm unsure how that works on EAS.
Additionally, it'd be great to have the expo-orbit:// schema documented so that we could have an automated PR comment that simply opens Orbit. Unfortunately, getting native app schemes working in PR comments is frustrating..
Additional context
No response
The text was updated successfully, but these errors were encountered:
dereklucas
changed the title
Open a specific update or channel
Feat: Open a specific update or channel
Dec 6, 2023
dereklucas
changed the title
Feat: Open a specific update or channel
feat: Open a specific update or channel
Dec 6, 2023
Is your feature request related to a problem? Please describe.
We use a pattern of development where we have infrequent builds but frequent updates. We ship a new build when the native code in our dev client changes. Then, whenever a PR is opened we create a channel and ship an update on that channel. Then, we use the dev client build build to load those updates. This lets us QA our code changes without the time sink of native app builds.
Describe the solution you'd like
Ideally
expo-orbit://u.expo.dev/[project ID]?channel-name=pr-875
would open a dev client in the simulator and load the update. Likely, we'd need to specific the build to use as well, but I'm unsure how that works on EAS.Additionally, it'd be great to have the
expo-orbit://
schema documented so that we could have an automated PR comment that simply opens Orbit. Unfortunately, getting native app schemes working in PR comments is frustrating..Additional context
No response
The text was updated successfully, but these errors were encountered: