google-play-core

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

What purpose does appUpdateInfo.isUpdateTypeAllowed (AppUpdateType.IMMEDIATE) serve in Android In-App Update API?

左心房为你撑大大i 提交于 2019-11-30 04:16:05
问题 I have been following In-App update API in Android for quite some time now and I am unable to find any relevance of the following line: appUpdateInfo.isUpdateTypeAllowed(AppUpdateType.IMMEDIATE) -- appUpdateInfo.isUpdateTypeAllowed(AppUpdateType.FLEXIBLE) This isUpdateTypeAllowed() method has been used in the code snippet below in Android Documentation: https://developer.android.com/guide/app-bundle/in-app-updates#update_readiness. Moreover, the above two method calls return true in all the

In-App Update API showing UPDATE_NOT_AVAILABLE while testing on debugging device

假装没事ソ 提交于 2019-11-29 14:57:11
问题 I am trying to integrate the new In-App Update API but I cannot able to test it's implementation. Seems like my code is fine therefore I read the Troubleshoots and am not able to understand 2 points in this document Make sure that the app that you are testing is signed with the same signing key as the one available from Google Play. How can I sign with same signing key in debug mode while installing Apk on Connected device?. If the app you are testing doesn’t appear with an available update,