[Proposal] Added Fastlane Setup For App Release Automation #5909
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a proposal for adding Fastlane into the codebase for better app automation.
In short, fastlane is an app automation tool that helps automating deployments to different store providers (e.g: App Store & Play Store).
I have added only the android pipeline as I dont have access to macbook for ios. My current setup pipeline will allow hexa to publish play store deployment with just one click and make it seamless.
Some of the details about my setup below
Inside
android/fastlane/Fastfile
the configuration for the app automation can be found and modify for future changes.Inside
android/fastlane/Appfile
aplay_store_secretKey.json
key should be present which can be found from hexa playstore configuration center AKA Google Developer Console.By setting up above config files, this should be up and running within no time.
Also @Parsh can you please let me know if you are using any CI system? If not I can prepare the application CI/CD pipeline in a easy plug & play model. This will also include testing with the CI/CD.
In the image you can find that this fastlane setup can successfully build and push the app to specific store provider.
the built .apk is unsigned because I haven't setup the google play console but this should be signed when connected with appropriate store.