Skip to content
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

Pick a pre-release distribution method for Android #20

Closed
markholland opened this issue Jan 29, 2018 · 4 comments
Closed

Pick a pre-release distribution method for Android #20

markholland opened this issue Jan 29, 2018 · 4 comments
Assignees
Labels

Comments

@markholland
Copy link
Collaborator

On iOS right now master deploys to internal TestFlight.

We need to pick an equivalent for Android.

  • Play Store has Alpha/Beta lanes
  • TestFairy is mentioned frequently
  • HockeyApp
@robbiemccorkell
Copy link
Contributor

For iOS, I've been adding everyone from the team to testflight, but I noticed that only "iTunes Connect" users can get updates for every pushed build and there's a small limit to how many users you can have (and arguably the roles give too much access for everyone).

Creating beta tester groups is fine for numbers, but you can only manually give them access to certain builds rather than every build we push, and sometimes it requires app store review.

One of the above tools might be better, and a bit more lenient, for us to use on iOS too.

@markholland
Copy link
Collaborator Author

Agreed, I'll work on getting master deploying both platforms to HockeyApp.

I'm picking HockeyApp as they've been around for a long time and I actively use them.

I'll be leaving TestFlight as is for stakeholder sign off as that is the shortest path of getting a signed off build to the App Store.

@markholland markholland self-assigned this Feb 3, 2018
@markholland
Copy link
Collaborator Author

Current blocker is where to store the Android keystore for release signing.

We could host the keystore somewhere and have CircleCI curl it which seems to be what most people go for when faced with an open code base.

I'm going to investigate this further using a self generated keystore that is ok to be compromised.

@markholland
Copy link
Collaborator Author

Closing this as we have HockeyApp for Android and iOS is in progress

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

No branches or pull requests

2 participants