-
Notifications
You must be signed in to change notification settings - Fork 22
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
Add ability to generate apks for different flavors via circle-ci for live stage #1096
Comments
Related: #1028 |
- helps with generating flavor specific prod APKs
Renamed keystore files to |
does this need update - https://avni.readme.io/docs/release-process-for-the-cloud#circleci-build also this - https://avni.readme.io/docs/flavouring-avni#steps-to-do-to-get-build-via-circle-ci objective - can I follow these steps and generate my own apk? |
No changes to the steps required for building apks via circleci. Updated both the above docs for changes in steps for building prod APK locally. |
@1t5j0y I think upload translations not done for live stage. Just realised recently. |
Added into scope of this card and implemented. |
Currently apk generated in the live stage is not signed with the right keystore. This causes confusion when for some reason this apk need to be shared with external client or need to be used for internal testing.
Analysis notes - options:
make release_prod_universal_without_clean
instead of usingbundletool.jar
to generate universal apk from bundleAdditionally, deploy platform translations while building live stage.
The text was updated successfully, but these errors were encountered: