google-play-console

问题 I've successfully completed the publishing process for an APK to the Internal Test Track. But when I try to view the App for download on the Google Play Store using the "VIEW ON GOOGLE PLAY" link in the screenshot below... ...it opens a new window with the following error: I've also tried using the testers link "download it on Google Play." below... ...but it results in the same message stating the App can't be found. This is the first time the App has been published and it's being done on

问题 This is a question about package names in android. I currently have two build flavors in gradle. Production and Staging. I have created a google play store account and i want users to alpha and beta test my app. The staging app currenly has a package name of: com.mobile.myapp.staging while the production flavor has a package name of com.mobile.myapp. so we have com.mobile.myapp.staging vs com.mobile.myapp in the end i clearly want to promote com.mobile.myapp to production not the staging. but

问题 I have a Unity project that I'm switching from APKs to AABs (app bundles). Previously, when I was building it as an APK, the Google Play Console told me the APK was 64-bit compliant. Now that I'm building an aab, I'm getting the warning: 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 I have both ARM7 and ARM64 architectures set. I am excluding x86. When I open the

问题 Ok, I want to preface that I have tried multiple solutions such as: Android Studio - Google map still blank on real Android device Android Google Maps API in Release not working I've tried to obtain the SHA1 fingerprint, and added those "Restrictions" to the Google Developer Console API Credentials. Also tried hardcoding the API into the manifest (can't find the link that recommended this). At this point, I've narrowed it down to these possible issues: 1) The keystore I am using has the

问题 While I was uploading an update for my app on google PlayStore, it showed a warning that said that my app must have target sdk >= 28 until August. My app uses target sdk = 27 Question What if I don't do that?? PlayStore does not say what will happen to those who don't make these changes... Should I worry about it and try refactoring my app? Why I am asking? I am using a library which is not working well with targetSDK 28 as it gives me errors. 回答1: Google set new requirements since this year,

问题 I have an existing app published to production and beta tracks that require SMS permissions. In order to comply with Google's recent policy changes on these permissions I have removed all SMS permissions and have new versions with higher version codes that do NOT require these permissions sitting in both internal-test and alpha tracks. I am unable to either promote these compliant versions to beta or production tracks or upload new higher versions directly to beta or production tracks. I am

问题 I've just received this message from Google Play but I'm not collecting the Advertising ID. Reason for warning: Violation of Usage of Android Advertising ID policy and section 4.8 of the Developer Distribution Agreement Google Play requires developers to provide a valid privacy policy when the app requests or handles sensitive user or device information. We’ve identified that your app collects and transmits the Android advertising ID, which is subject to a privacy policy requirement. Is it

问题 Got this warning while publishing the app: We’ve detected that your app is using an old version of the Google Play Developer API. From December 1 2019, versions 1 and 2 of this API will no longer be available. Update to version 3 before this date. https://android-developers.googleblog.com/2019/03/changes-to-google-play-developer-api.html I'm wondering why I got this warning as I'm not using Google Play developer API explicitly. Can anyone tell me what does it mean and how to update it to v3?

问题 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 回答1: 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"

问题 I cannot deploy the .abb nor .apk as I keep getting the 64-bit requirement error in the Google Play Console. I have tried everything from this answer: Unity Export Android 64-bit but still the same problem. Unity3D version: 2017.4.30f1 NDK: r13b (Unity is not supporting newer versions but this should not be a problem) SDK API Level: 28 JDK: 1.8.0_221 Player Settings: When the Unity builds the package I can see it is building for 64-bit devices so I don't get what is the issue. 回答1: Build your