android-app-bundle

PlatformException(sign_in_failed, com.google.android.gms.common.api.ApiException: 10: , null) when using Flutter to build an appbundle

由 南笙酒味 提交于 2019-12-11 14:29:43
问题 I'm building a Flutter app with firebase_auth and google_sign_in. Everything was working well for a while and all of my existing users on the released product have not experienced any problems, but a while back I started getting reports that new users couldn't log in. I didn't think much of it until the reports started to accumulate. I found that they were getting the error posted in the title. I spent a ton of time investigating... I've gone through all of the other StackOverflow entries for

How to use “libsu” library (or adb) to install split APK files on Android Q?

由 自作多情 提交于 2019-12-11 01:07:21
问题 Background Using root, I know that for a single APK file, we can use the "libsu" library (here) to install as such: val installResult = Shell.su("pm install -t \"$filePath\"").exec() And if that failed (fails on new Android versions, not sure from which), as such (written about this here): val installResult = Shell.su("cat \"$filePath\" | pm install -t -S ${apkSource.fileSize}").exec() I also know that things got quite messy when it comes to installing split APK files (as shown here). First

Google Play crash logs not symbolicated with Android App Bundle

由 北战南征 提交于 2019-12-10 04:35:53
问题 We have recently updated our apps to use Android App Bundles (aab) and to also include arm64 native libs. Since doing so, our crash logs in native code in the 'Google Play Console'->'Android Vitals'->'ANRs & Crashes' are not symbolicating correctly (java callstacks symbolicate fine). A snippet from a typical callstack looks like this: #21 pc 000000000015addc /data/app/com.mycompany.mygame-2/split_config.arm64_v8a.apk #22 pc 0000000000293768 /data/app/com.mycompany.mygame-2/split_config.arm64

Instant app with Dynamic Features always show Disambiguation dialog with 1 option

由 為{幸葍}努か 提交于 2019-12-09 06:31:59
问题 I'm experimenting with Dynamic Features and Instant Apps. To navigate between various features, I use Deep Links. Each time I navigate to another Activity, I see the disambiguation dialog for less than 1 second, with 1 app listed. Notice how the options for "Once" and "Always" (in dutch) are greyed out. Sample Github Project I created a minimalistic sample, that matches my current structure on Github. Requires Android Studio 3.5 - RC2 Some Context: I'm quite confident, the deeplinks are

Resource Not Found error res/drawable/abc_switch_thumb_material.xml after adding SwitchCompat in Android App Bundle

由 雨燕双飞 提交于 2019-12-07 04:46:21
问题 I Know this Question has been asked several times i have read them all and have matched all dependencies so that they have same versions but this error only started to happen after adding Switch Compat as you can also see that by going through the crash report by fabric . This Error is happing not on all devices but to some by the crash report , also it has no specific Android for this crash. One More thing i am using beta versions of android because of Android App Bundle and this thing does

Generate Universal APK from Android App Bundle

由 ﹥＞﹥吖頭↗ 提交于 2019-12-07 04:13:42
问题 I have an app bundle file, now I want to generate a universal APK that can be installed to all devices. I have tried to use this command to generate universal APK: $bundletool build-apks --bundle=myapp_bundle.abb --output=myapp.apks --universal However, what I got is .apks (not .apk) where I cannot install directly to any devices. Anyone know how to get a universal .apk file instead of .apks? Thank you very much. 回答1: Use either the extract-apks or the install-apks command to respectively

Android In App Updates - Not able to detect the update in AppUpdateInfo

由 久未见 提交于 2019-12-06 04:37:40
Some log statements are thrown when we use, Task<AppUpdateInfo> appUpdateInfoTask = appUpdateManager.getAppUpdateInfo(); appUpdateInfoTask.addOnSuccessListener(appUpdateInfo -> { 2019-06-13 18:30:40.556 28375-28375/com.marsplay.debug I/PlayCore: UID: [10312] PID: [28375] AppUpdateService : requestUpdateInfo(<"package name here">) 2019-06-13 18:30:40.556 28375-28584/com.marsplay.debug I/PlayCore: UID: [10312] PID: [28375] AppUpdateService : Initiate binding to the service. 2019-06-13 18:30:40.560 28375-28375/com.marsplay.debug I/PlayCore: UID: [10312] PID: [28375] AppUpdateService :

Verify non-Google Play app installs using Play core library

由 时间秒杀一切 提交于 2019-12-05 21:58:17
问题 Some context: Most of us may have faced this ResourceNotFoundException when we migrated to Android app bundle release method. It is evident that the issue is because of Side-loading the app. Reference here. Google recently announced solution to this problem. Using play core library we can identify whether the app is side-loaded or not (Identifies the missing split apks). If the app is side-loaded it shows " Installation failed " popup and redirects to play store, where user can properly

Resource Not Found error res/drawable/abc_switch_thumb_material.xml after adding SwitchCompat in Android App Bundle

由 孤者浪人 提交于 2019-12-05 10:16:58
I Know this Question has been asked several times i have read them all and have matched all dependencies so that they have same versions but this error only started to happen after adding Switch Compat as you can also see that by going through the crash report by fabric . This Error is happing not on all devices but to some by the crash report , also it has no specific Android for this crash. One More thing i am using beta versions of android because of Android App Bundle and this thing does not happen in non bundles that is Apk. Fatal Exception: java.lang.RuntimeException: Unable to start

Verify non-Google Play app installs using Play core library

由 梦想与她 提交于 2019-12-04 03:29:36
Some context: Most of us may have faced this ResourceNotFoundException when we migrated to Android app bundle release method. It is evident that the issue is because of Side-loading the app. Reference here. Google recently announced solution to this problem. Using play core library we can identify whether the app is side-loaded or not (Identifies the missing split apks). If the app is side-loaded it shows " Installation failed " popup and redirects to play store, where user can properly install the app via the Google Play store. Problem: Everything works fine until the installation of missing
订阅 android-app-bundle