android-app-bundle

问题 I try to build different Android app bundles via productFlavors. To keep and test the files I need a fixed file name. For APK's I have the following working code: applicationVariants.all { variant -> if (variant.buildType.name.equals("release")) { variant.outputs.all { output -> outputFileName = "${applicationId}-${versionCode}-${variant.flavorName}.apk" } } if (variant.getBuildType().isMinifyEnabled()) { variant.assemble.doLast { copy { from variant.mappingFile into variant.outputs[0]

问题 I have created android build of my Flutter application. Then I created an internal testing release. It is showing a warning This App Bundle contains native code, and you've not uploaded debug symbols. We recommend you upload a symbol file to make your crashes and ANRs easier to analyze and debug. Basically what I had to do is add following to build.gradle file according to the link they show. android.buildTypes.release.ndk.debugSymbolLevel = { SYMBOL_TABLE | FULL } I assume it is android/app

问题 When uploading an aab to the android play store console the versionCode is showing a much higher and completely different number than expected. The version Code is not showing as written in the gradle (targetSdkVersion) file of the app like it does when uploaded as a single apk. I've built several apks in the past. I wanted to decrease apk size for users. to accomplish this I've built my app as an aab and successfully uploaded the file into firebase console. The problem manifests itself at

问题 Together with a friend I have created an Android app to organize school grades. The app works fine on my device and on most user devices, however there is a crashing rate over 3 percent, mostly because of java.lang.UnsatisfiedLinkError and occurring on Android versions 7.0, 8.1 as well as 9. I've tested the app on my phone and on several emulators, including all the architectures. I upload the app to the app store as an android-app-bundle and suspect that this could be the source of the

问题 So I am currently trying to create an Appbundle so I can upload my app to the google play store. Unfortunately, I encountered a problem with the signature release portion of the project. Below is the copy of the error from the terminal: FAILURE: Build failed with an exception. * What went wrong: Execution failed for task ':app:packageRelease'. > com.android.ide.common.signing.KeytoolException: Failed to read key key from store "/Users/herb/Downloads/morningly/android/app/key.jks": keystore

问题 I am using some libraries in my dynamic feature module. These libraries are Adding some providers to the manifest. For example in my build.gradle file in the dynamic module: dependencies { ... implementation 'com.github.esafirm.android-image-picker:imagepicker:1.11.1' ... } This library adds the following tag to the manifest: <provider android:name="com.esafirm.imagepicker.helper.ImagePickerFileProvider" android:authorities="{$applicationId}.imagepicker.provider" android:exported="false"

问题 I set android:extractNativeLibs="true" and target to Android 29 to make my shared libs extracted to /data/app/%package%/... by Android. If works just fine with APK to workaround Android 10 permissions issue. Recently i had to switch to AAB due to increased to 150Mb download size as my APK size exceeds Google Play limit of 100Mb. When testing APK installation from AAB ["APK from app bundle" deploy option in Android Studio] i noticed /data/app/%package%/.. is empty (in contrast to pure single

问题 I want to start publish my app as AAB. I successfully build my build.aab file and decide to try install app on my phone. I use next way 1) Build APK set from aab file with command: java -jar bundletool.jar build-apks --bundle=*path to aab* --output=*path to apks* --connected-device --ks=*android debug keystore path* --ks-key-alias=androiddebugkey --adb=*path to adb* 2) Install with next command: java -jar bundletool.jar install-apks --apks=*path to apks* --adb=*path to adb* App is

问题 I have used PWA2APK to upload the first version of my React app to Google Play. It worked great. But every time I try to update the app by uploading a new version, I get the following: You uploaded an APK that is not signed with the upload certificate. You must use the same certificate. The upload certificate has fingerprint: SHA1: ******************* and the certificate used to sign the APK you uploaded has fingerprint: SHA1: ********************** Your APK or Android App Bundle needs to

问题 I have used PWA2APK to upload the first version of my React app to Google Play. It worked great. But every time I try to update the app by uploading a new version, I get the following: You uploaded an APK that is not signed with the upload certificate. You must use the same certificate. The upload certificate has fingerprint: SHA1: ******************* and the certificate used to sign the APK you uploaded has fingerprint: SHA1: ********************** Your APK or Android App Bundle needs to