You Uploaded a Debuggable Apk for Android App Bundle
Generating and deploying Android app bundles
Creating an Android App Bundle with Bitrise is almost the same as generating an APK. All yous have to do is tweaking a few Step inputs to compile an Android App Bundle (.aab) file from your code, then get the package signed and deployed to Google Play Shop.
Step versions supporting bundle cosmos
The following Steps must be of the indicated version or newer - older versions of the Steps practise Non back up bundle creation.
-
Android Build 0.10.0 or newer
-
Gradle Runner i.9.0 or newer
-
Android Sign 1.3.0 or newer
-
Deploy to Google Play 1.half-dozen.0 or newer
Generating an Android App Bundle file
You can create an Android App Bundle with either the Gradle Runner Step or with the Android Build Step.
Using the Gradle Runner Pace
-
Open your app on Bitrise.
-
Become to the Workflow tab.
-
Select a Workflow from the dropdown menu.
-
Insert the Gradle Runner Step after the Android Unit of measurement Test and Android Lint Steps in your Workflow (if the build Step is non already in that location).
-
Click the Config section of Gradle Runner .
-
In the Gradle task to run input field, set, for example,
bundleReleaseorbundleDebugto create a bundle of your project.
This style the Pace will generate an Android App Packet instead of an APK.
If you lot wish to generate an Android App Bundle and an APK in one workflow, you lot can specify an additional task in the Gradle task to run input field:
Using the Android Build Pace
You tin generate an Android App Bundle for your Android app with our Android Build Footstep too:
-
Open up your app on Bitrise.
-
Go to the Workflow tab.
-
Select a Workflow from the dropdown menu.
-
Add the Android Build Step later on the Android Unit Test and Android Lint Steps in your Workflow (if the build Step is non already there).
-
Provide the root directory of your Android project in the Project Location input field.
-
Go to Build type and select
aabas build type.
If you wish to generate an APK and an Android App Packet in one workflow, add two Android Build Steps later each other and configure i to build an Android App Bundle and the other to build an APK.
Deploying your Android App Packet to Google Play
Deploying an AAB file isn't significantly different from deploying an APK to Google Play.
If you want to check the bundle prior to app store distribution, you tin can add the Deploy to Bitrise.io Step after the Gradle Runner / Android Build Steps. It uploads the bundle into the Artifacts tab of your Build's folio.
Setting upward Google Play deployment for the first fourth dimension
Deploying to Google play publishes your app to Google's online store. When you do information technology for the get-go time, this requires a bit more piece of work than simply deploying to bitrise.io. Once the necessary configurations are in place, it becomes very simple.
When configuring Google Play deployment for the starting time time, yous need to link your Google Play Developer account to an API project, fix API access, and upload the service business relationship JSON cardinal to Bitrise.
-
Upload the kickoff AAB or APK manually to Google Play using the Google Play Panel.
-
Link your Google Play Developer Panel to an API project.
-
Gear up API Admission Clients using a service account: Delight notation when you create your service account on the Google Programmer Console, you accept to choose
jsonas Key Type . -
Grant the necessary rights to the service account with your Google Play Panel. Go to Settings , then Users & permissions , and so Invite new user . Due to the way the Google Play Publisher API works, you lot take to grant at least the post-obit permissions to the service business relationship:
-
Access level: View app information.
-
Release management: Manage production releases, manage testing track releases.
-
Store presence: Edit store listing, pricing & distribution.
-
-
As an optional pace, you can add translations to your Shop Listing: Interpret & localize your app.
-
Open your app on Bitrise.
-
Go to the Workflow tab.
-
Go to the Code Signing tab and upload the service business relationship JSON key into the GENERIC FILE STORAGE .
Deploying to Google Play
Deploying to Google Play requires a signed APK or AAB file and the Google Play Deploy Footstep.
-
If you're trying to deploy your app for the first time, brand sure your Google Play configuration is fix correctly.
-
Open your app on Bitrise.
-
Go to the Workflow tab.
-
Become to the Lawmaking Signing tab and re-create the Surround Variable primal which stores your uploaded the service account JSON fundamental file's URL.
-
Copy the Surround Variable central which stores your uploaded file'southward URL.
For case:
BITRISEIO_SERVICE_ACCOUNT_JSON_KEY_URL. -
Open your Workflow and add the Google Play Deploy Step to it.
-
In the Service Account JSON cardinal file path input, paste the Environment Variable which was generated when you uploaded the service account JSON cardinal in the GENERIC FILE STORAGE . Too the generated Env Var, you tin can also add a file path right in the Footstep's input field where the file path can be local or remote too:
-
For remote JSON key file you lot can provide whatever download location every bit value, for instance,
https://URL/TO/key.json. -
For local JSON key file y'all tin can provide a file path url as value, for example,
file://PATH/TO/key.json.
-
-
In the Package name input, add the package proper name of your app.
-
In the Rail input, add the track where you desire to deploy your APK (for example, alpha/beta/rollout/production or any custom rail you set).
That's all! Start or schedule a build and share the URL with external testers or distribute your app on an app store of your selection!
Source: https://devcenter.bitrise.io/en/deploying/android-deployment/generating-and-deploying-android-app-bundles.html
0 Response to "You Uploaded a Debuggable Apk for Android App Bundle"
Post a Comment