New Android App Bundle and target API level requirements in 2021 lazarus / 43-Android ---------------------------------------------------------------------- ADiV · 2020-11-27 10:31 New Android App Bundle and target API level requirements in 2021 19 November 2020 Posted by Hoi Lam, Developer Relations Engineer, Android Platform Android app bundle image In 2021, we are continuing with our annual target API level update, requiring new apps to target API level 30 (Android 11) in August and in November for all app updates. In addition, as announced earlier this year, Google Play will require new apps to use the Android App Bundle publishing format. This brings the benefits of smaller apps and simpler releases to more users and developers and supports ongoing investment in advanced distribution. Over 750,000 apps and games already publish to production on Google Play using app bundles. Top apps switching save an average size of 15% versus a universal APK. Users benefit from smaller downloads and developers like Netflix and Riafy see higher install success rates, which is especially impactful in regions with more entry level devices and slower data speeds. Developers switching can use advanced distribution features such as Play Asset Delivery and Play Feature Delivery. We value your feedback and plan to introduce further features and options for Play App Signing and Android App Bundles before the switchover. More information: https://android-developers.googleblog.com/2020/11/new-android-app- bundle-and-target-api.html ---------------------------------------------------------------------- ADiV · 2020-11-27 10:44 Creating an App Bundle is quite simple we will only have to create this "gradle-local-build-bundle.bat": Code: Pascal  [Select][+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i set Path=%PATH%;c:\laztoapk\downloads\android-sdk-windows\platform- toolsset GRADLE_HOME=c:\laztoapk\downloads\gradle-6.6.1\set PATH=%PATH%;%GRADLE_HOME%\bingradle clean bundle --info  If we want it to be signed to be able to upload it to Google Play, the easiest thing is to add the following to build.Gradle, which will also help us to automatically sign the Apk: Code: Java  [Select][+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i     ...    defaultConfig { ... }     signingConfigs {        release {          // You need to specify either an absolute path or include the          // keystore file in the same directory as the build.gradle file.          storeFile file("myapp.keystore")            storePassword "mystorepassword"            keyAlias "mykey-alias"            keyPassword "mykeypassword"        }    }     buildTypes {        release {            signingConfig signingConfigs.release                 }    }  Tested in my shopping list app: https://play.google.com/store/apps/details?id=tr3e.MarkListFree ---------------------------------------------------------------------- Segator · 2020-11-27 12:28 I use the sign script like that because i can't create a google development account ( i am cuban), but this need integrate to the smartdedisign code because it delete it from build.gradle constantly, about the API 30 i download the Android R things and i can select the API 30 target, only up to 29 i can select. ---------------------------------------------------------------------- ADiV · 2020-11-27 13:47 Quote from: Segator on November 27, 2020, 01:28:32 pmI use the sign script like that because i can't create a google development account ( i am cuban), but this need integrate to the smartdedisign code because it delete it from build.gradle constantly, about the API 30 i download the Android R things and i can select the API 30 target, only up to 29 i can select. The API 30 is not yet available but the App Bundle is, it can also be generated without signing, but if you do not use Google Play, none of the above is necessary. ---------------------------------------------------------------------- Segator · 2020-11-27 17:35 QuoteThe API 30 is not yet available but the App Bundle is, it can also be generated without signing, but if you do not use Google Play, none of the above is necessary.but i hope that i can use Google play in the future  ADiV share the optimization script a gain you not give time to copy it ---------------------------------------------------------------------- ADiV · 2020-11-28 18:38 Quote from: Segator on November 27, 2020, 06:35:33 pmQuoteThe API 30 is not yet available but the App Bundle is, it can also be generated without signing, but if you do not use Google Play, none of the above is necessary.but i hope that i can use Google play in the future  ADiV share the optimization script a gain you not give time to copy it  The code obfuscation script does not work for LAMW as it changes the names of Java functions and the native code cannot bind. ---------------------------------------------------------------------- ADiV · 2020-12-03 18:28 With the latest LAMW update we can sign our apk or bundle more easily: First we will execute "release-keystore" if we do not have the signature created. Then we will fill in the signature file "gradle.properties" as follows: Code: Pascal  [Select][+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i RELEASE_STORE_FILE = yourapp.keystoreRELEASE_STORE_PASSWORD = yourpasswordRELEASE_KEY_ALIAS = yourappaliaskeyRELEASE_KEY_PASSWORD = yourpassword And to finish we close and open the project and it will automatically include the signature. ---------------------------------------------------------------------- Segator · 2020-12-03 18:44 That is a great news!!! ---------------------------------------------------------------------- jmpessoa · 2020-12-03 19:59 Added new "Docs" to LAMW github "How to Sign apk or bundle using gradle by ADiV.txt" Thank you!