fileinformation

[fileinformation]

Step by step instructions to Generate and Extract APK Files

In Google, I/O 2018, Android App Bundle, another record design was acquainted with dispersing Android applications through Google Play. Later in 2019, Google began prescribing designers to transfer new applications/refreshes in .aab design rather than customary .apk. The primary target of the Android App Bundle is diminishing the size of the application you download from Play Store. It is an assortment of various APKs created progressively for different gadget setups. Assuming you need to introduce .aab record outside of Play Store, you wanted to initially extricate APK documents from AAB and introduce them physically on your Android gadget.

For instance, if an Android application has numerous strings .vcf files for various dialects and your gadget default language is set to English. A .apk record will be created powerfully for your gadget barring any remaining language documents to lessen the .apk size.

This component comes handy according to a client perspective yet for engineers and analyzers, it added more migraine. Since it is unimaginable to expect to introduce a .aab document like APKs, you wanted to either first transfer it to Play Store for testing or physically create APK records from Android App Bundle (.aab). When various APKs or widespread APK record is removed from .aab, you can introduce the application on various gadget setups.

 Changing over torrent App error (.aab) to APK File

In the wake of creating the Android App Bundle from Android Studio or your beloved IDE, you wanted to initially test how the produced APKs act when sent on nearby mobiles. The speediest way of doing this is changing over the .aab document to APK and introducing it conventionally.

To separate APK records from Android App Bundle, we're utilizing the bundle tool, which is an open-source order line apparatus accessible on GitHub. This instrument is for controlling the Android App Bundle to produce APK set chronicle (.apks) document. Once the ".apks" record is produced utilizing the bundle tool, we can remove the APK documents by changing the document to a .zip design.

Here is how you can utilize the bundle tool to produce .apks document record from Android App Bundle and concentrate .apk documents:

 Stage 1: Download bundle tool order line device

First of all, download the most recent rendition of the bundle tool container record from GitHub and save it inside an organizer on the Desktop. At the hour of composing this article, the most recent rendition of the bundle tool is 0.10.2 and for straightforwardness, change the record name from bundle tool-all-0.10.2.jar to bundletool.jar

 Stage 2: Generate APK Set Archive tmp file from .aab

Duplicate your Android App Bundle (.aab) record to a similar envelope where you have downloaded the bundletool.jar in past advances. This is vital and you should ensure both bundletool.jar and .aab documents are in a similar envelope each time you run the bundle tool order.

As displayed in the screen capture, the name of my Android App Bundle is NHL.aab and both "bundletool.jar" and "NHL. aab" documents are in a similar organizer. For this instructional exercise, we are utilizing the AAB document of our Notification History application.

Presently open the Command Prompt (Windows) or Terminal (Mac) and change the catalog to your Desktop envelope utilizing the CD order. To create an APK set document (.apks) record containing diverse APK documents of all gadgets setups your application upholds, run the form asks order as displayed beneath.

 java - container bundletool.jar assemble apks - bundle=nhl.aab - output=nhl.apks

·        bundletool.jar – The name of .container record you downloaded from GitHub

·        NHL.aab – Your Android App Bundle record name

·        NHL. apks – The name of the yield record. It is a .apks record. Try not to mistake it for the customary .apk document.

  Stage 3: Extract APK Files

Once the "NHL. asks" record is produced, it is exceptionally simple to remove APK documents from it. You should simply, rename the "NHL.apks" document to "nhl.zip" and separate it typically utilizing a ZIP record extractor. You will presently discover a ton of APK documents in parts and independent elements envelopes.

Presently you have effectively changed over the .aab document to .apk records and you can introduce them on your gadget ordinarily. This is how you can introduce the .aab document on an Android gadget.

Stand by it's not finished at this point. Did you see any issue with the above order? Indeed, it is producing a lot of Debug APK records and you don't know concerning which one you wanted to introduce? Imagine a scenario in which you need marked APKs or an all-inclusive marked APK from Android App Bundle. Luckily, the bundle tool accompanies various banners for extricating the required APK from the .aab document.

 Creating Signed APKs utilizing your Keystore

To create marked APK documents with your Keystore record, run the underneath order.

java - container bundletool.jar fabricate apks - bundle=nhl.adb - output=nhl.apks - ks=keystore.jks - ks-pass=pass:your_keystore_password - ks-key-alias=your_key_alias - key-pass=pass:your_key_password

 This will again create an "NHL. asks" document and you wanted to rename it to "nhl.zip" and extricate the compress record to see marked apks in the two parts and independent organizers.

 Creating a Universal APK from Android App Bundle

Assuming you need to produce just one single APK from your .aab document, run the underneath order.

 java - container bundletool.jar construct apks - bundle=nhl.aab - output=nhl.apks - mode=universal

 This order will create the NHL. apks document and again you wanted to rename it to nhl.zip and separate it to get a universnal.apk record.

 Overwriting existing .apks record

Assuming you need to overwrite the old .apks record with the upgraded one, you wanted to simply add the – overwrite banner to your order as displayed underneath.

 java - container bundletool.jar construct apks - bundle=nhl.aab - output=nhl.apks - overwrite

 Separating Signed Universal APK record from Android App Bundle

Presently how about we join all the above banners to create a solitary general APK document and overwrite the current APK chronicle if currently accessible.

 java - container bundletool.jar assemble apks - bundle=nhl.aab - output=nhl.apks - overwrite - mode=universal - ks=keystore.jks - ks-pass=pass:your_keystore_password - ks-key-alias=your_key_alias - key-pass=pass:your_key_password

 After running this order, you should rename the created "NHL.apks" record to "nhl.zip" and extricate it to track down the marked "universal.apk" document.

 There are not many further developed banners like - gadget spec, - an associated gadget, - gadget id to create APK and introduce Android App Bundle on associated or explicit gadget setups. Aside from them you additionally have to remove apks and get-size complete orders for more use-cases.