Skip to content

Handling Testflight and Android Beta deployments #51

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

Open
codytooker opened this issue Jan 8, 2020 · 1 comment
Open

Handling Testflight and Android Beta deployments #51

codytooker opened this issue Jan 8, 2020 · 1 comment

Comments

@codytooker
Copy link

Is there a recommended way to handle the different app-sync environments based on if the app was installed from the app store or through testflight? Same for android, either the play store or the Android Beta program?

The problem is that the normal flow is to promote builds from beta to production. This means we don't create a new binary and don't have the ability to inject the app-sync environment keys.

@prestopasto
Copy link

I was wondering this too. My only thought so far was to hide something in my app settings to switch to the Staging pipeline. Maybe something along the lines on Android's clicking the build number to enable the developer options menu.

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

No branches or pull requests

2 participants