google-play-console

TL;DR Google Play Console forces to show Permissions Declaration Form (see below) as soon as "Create Release" button clicked even if updated APK uploaded without READ_CALL_LOG which caused the warning email from Google before. Question How to avoid the Permissions Declaration Form which looks irrelevant if releasing updated APK without sensitive permissions? Problem in details PRODUCTION and ALPHA releases were submitted with READ_CALL_LOG permission before Google emailed about prohibit to use it. Now, during creating new release and once clicking "Create release" button -- it disappears in

I have published my application in alpha testing for testing purpose. Now I want delete it permanently from listing. So, Is it possible to delete published application in alpha mode? If your app is in Alpha and no one has downloaded it. You have to unpublished your app first and then contact Google. They will delete your app for you. I had them delete 1 app for me. If you has not published your application yet you can delete it. Once you publish it you can only unpublish it. So you can delete it. You can only unpublish but cannot delete it. it will not display to user but it will be in your

I have generated my SHA1 code from my keystore but when I try to create an OAuth client 2.0, Google game console is giving me the error: "Certificate fingerprint is invalid". Anyone knows why this happens? How do I fix this? I've contacted Google Play Developer Support about this issue (I've got a same problem). Here is their answer : Please ensure the key is set to 2048 bit and is valid for at least 25 years. I've tried it, but sadly my debug.keystore is still not getting accepted, maybe there will be some luck on your side. $ keytool -genkey -v -keystore debug.keystore -storepass android

Android app bundle upload failed with error Invalid SplitApkBundle. The bundle targets unknown languages: [gr] Android Studio version 3.5 I tried Clean & rebuild Invalidate cache/restart RavenYang I had the same issue. Invalid SplitApkBundle. The bundle targets unknown languages:[cb] I solved by setting DSL to stop aapt package building the wrong language targets. My app supports English and Chinese, therefore resConfigs only needs en and zh. defaultConfig { ... resConfigs "en", "zh-rTW", "zh-rCN" } Apply this to Android{} bundle { density { // Different APKs are generated for devices with

I've been trying to upload .abb to the google play console. When I upload it, it gives me this error: This release is not compliant with the Google Play 64-bit requirement The following APKs or App Bundles are available to 64-bit devices, but they only have 32-bit native code: 2. From 1. August 2019 all releases must be compliant with the Google Play 64-bit requirement. Include 64-bit and 32-bit native code in your app. Use the Android App Bundle publishing format to automatically ensure that each device architecture receives only the native code it needs. This avoids increasing the overall

It show this message This app does not meet the Google Play permissions policy relating to the use of SMS or CALL_LOG. You must fix this before March 9. 2019 or your app will be removed from Google Play. Note: if you have recently made a change, it can take up to 12 hours to update this message. My app on its previous version has this permission and apply for an exception when it was rejected I updated the app 2 weeks ago and removed this permission. But now I get this message. I also received this warning on my last app version. Explanation: You are receiving this warning because somehow