-
Notifications
You must be signed in to change notification settings - Fork 507
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
Firebase App Distribution with Fastlane #1293
base: master
Are you sure you want to change the base?
Conversation
…flict with CI format checks
We'll address this after v1.0. |
This item has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This item has been automatically closed as stale. |
@epicfaace - now we've got approval for releasing the app. @joshdholtz - please review or let us know how else we should go about this. |
@brunobowden I don't think this is relevant anymore -- closing it, but let me know otherwise. |
@epicfaace - it is something we should do at some point. Is it worth accepting the PR just so that it can stick around in the tree for when we pick it up later on? |
description
Setup fastlane for firebase app distribution (fixes #1044). Instructions for deploying this are in release/manual-build.md.
I've added one lane,
distribute
(for who-myhealth-production). When actually deploying to firebase app distribution, we should runbundle exec fastlane distribute
so that the app is deployed to who-myhealth-production.In order to test the fastlane integration, I replaced the app id in Fastfile with
1:1057717871229:android:4fbe832a3de230450dc714
(which is the app id in who-myhealth-staging) and then deployed to who-myhealth-staging.dependencies
Also added a Gemfile.lock -- this is needed to pin down dependencies used by fastlane (such as firebase_app_distribution).
The new dependency,
fastlane-plugin-firebase_app_distribution
, is also maintained by the fastlane team.