I've published multiple apps using flavors and each one have multiple apks using splits. At first few users complain that they getting error 963 when trying to download the app from google play store but now, after version update, the complains number increased significantly. lot of users complains that they get error 963 and cant download the update.
Is there anything I can do from my side to prevent it from happening?
The apks size are ~30MB each and I've added android:installLocation="preferExternal" to manifest.
Removing the android:installLocation attribute from the manifest seems to solve the issue.
Is there anything I can do from my side to prevent it from happening?
No. Some people publish articles how to solve the issue, but this is all from user perspective and is rather working the issue around, not fixing it. You, as developer, cannot do much about how google infrastructure or services work.
Related
My app is written on android native code and I got this warning on the play store console
Your app "appName" version code "xxxx" includes SDK com.segment.analytics.android:analytics or an SDK that one of your libraries depends on, which collects personal or sensitive data that includes but may not be limited to Advertising ID, Android ID identifiers. Persistent device identifiers may not be linked to other personal and sensitive user data or resettable device identifiers as described in the User Data policy.
ACTION REQUIRED: Upload a new compliant version AND deactivate the noncompliant version.
But I don't have that library on my project, the only libraries related to firebase that I have are these:
"com.google.firebase:firebase-crashlytics:17.4.0",
"com.google.firebase:firebase-analytics:18.0.2",
"com.google.firebase:firebase-perf:20.0.2",
"com.google.firebase:firebase-core:18.0.0",
"com.google.firebase:firebase-auth:20.0.1",
"com.google.firebase:firebase-messaging:21.0.1",
But I don't know how to solve this, should I update all of them and upload my app again and check if I received this warning again or not to see if it was solved? I need to solve this because I won't be able to upload more app versions in the following months.
Thank you for being so helpful, it's really appreciated.
Some people have asked me if I solved this, and the short answer is yes, I did. Unfortunately, nobody gave me a specific answer about how to solve it, and the problem is that I think I used a bazooka to kill a fly.
The process for solving this was this:
I updated all Firebase dependencies, I was using these:
com.google.firebase:firebase-crashlytics,
com.google.firebase:firebase-analytics,
com.google.firebase:firebase-perf,
com.google.firebase:firebase-core,
com.google.firebase:firebase-auth,
com.google.firebase:firebase-messaging
I update them using firebase-bom version 30.3.2
Also, I updated other google dependencies, I'm not 100% sure that this affected the solution, however, I want to document all just in case you are also using them, and you can consider it out.
com.google.android.gms:play-services-auth:20.2.0,
com.google.android.gms:play-services-auth-api-phone:18.0.1,
com.google.android.gms:play-services-analytics:18.0.1,
com.google.android.gms:play-services-base:18.1.0,
com.google.android.gms:play-services-location:20.0.0,
com.google.android.gms:play-services-maps:18.0.1
After using these versions, I uploaded the new build and did not see the problem again in the Google console for this version and later
Sorry for not being specific in the needed dependency to be updated, I didn't have a chance to test the combinations to discover them.
All of sudden google console started throwing an error message saying - "At least one of your app or app bundles contain an actions.xml file."
I have searched my entire app, there is no actions.xml.
Also used Analyze Apk tool of android studio to cross verify if any lib or other module may adding the actions.xml.
Here is one troubleshoot link from google (link) it describe the process To accept the Actions on Google Terms of Service.
But question remains the same that project doesn't contain any actions.xml.
Is it a console bug or I am missing anything.
This was very weird but when I tried to upload the apk after sometime it worked perfectly fine without any error messages.
As I rightly mentioned in the question there was no action.xml and action tag anywhere in my entire project.
It seems to be a console bug in my case.
It was a Google Play Console bug:
Thanks for your patience while our team investigated the behavior you experienced.
They have recently made some changes that should fix the problem. With the recent set of changes, please check to see if you are still experiencing the same issue. If so, I will be happy to see how else we can help.
Please ensure to clear your browser's cache and cookies first using the instructions available in our help center before accessing the Play Console again.
I'm trying to push an update in the Play Store and I came across the following error. I'm aware of the new target API requirement which will be in effect from November 1st, but as of now, I'm supposed to be able to push an update to play store right? If that's the case, I'm not sure why am I getting this error.
Could some one please help me?
Thank you
That's a warning, not an error. It even says "Warning" right there.
You should be able to publish it anyway. The August deadline only applies to new apps.
This warning does not (or should not) have the capacity to block your release. There are two possibilities:
your release is being blocked by some other error as well which you aren't noticing because of this warning
there is a bug in the Play Console
If it is the second option you should report it to the Play Console support team. You can contact them via the help menu in the Play Console, which is behind the "?" (Question Mark) icon. But the first option is more likely.
I contacted Google Play Store support and they told me the issue is caused because of the version code number of the app. Though I updated the version, I forgot to update the version code number.
I fixed the version code number and uploaded the APK to the play store and it worked.
Thank you
I'm suddenly getting this difference from the previous version when trying to upload a new version of my app to Play:
I use only default string values, most of them hardcoded, as my app only supports one language so far.
Anyway, I haven't changed anything related to locales/languages to this last update.
when googling about this, the only reference I fount was this link. I was using an outdated version of facebook sdk, but updating it didn't brought my Localizatons back... alse I don't use Corona SDK...
how will this affect my app's distribution? Is it like fewer people will have access to it? Or users will get some screens in the wrong language?
I had the opposite effect (like Seth said) after adding the "Google Play Services" library to my project. Maybe you removed this or another library (that had supported all of this languages) from your main project.
I have an app with 100k~ downloads on Play, which I started to develop like a year ago. Back then, it had the default crappy android UI. A month ago, I decided to include the ActionbarSherlock+HoloEverywhere libraries, so it could provide a much better user experience, with the Holo UI. Here comes the problem.
I got a few user reports, that they cannot update, since Play is keep telling them, their device is incompatible with the app. NOTHING changed besides adding and using the above mentioned libraries, so their device SHOULD still be compatible with my app. Here is what I know, and tried so far, including reports from the most helpful user, who cooperates with me, and want to use the app.
his old device broke, so it got replaced, and he couldn't install the updated version
on the new device, he can't install the old versions, which he could on the old device
the mentioned device is an atab5 MTK6577
the minimum API level is currently 8 (Android 2.2)
my app requests the following permissions:
android.permission.ACCESS_FINE_LOCATION
android.permission.ACCESS_NETWORK_STATE
android.permission.INTERNET
the features the device has to got are the following:
android.hardware.LOCATION
android.hardware.location.GPS
android.hardware.TOUCHSCREEN
I found a nice tool (http://codekiem.com/2013/02/13/market-helper/) , which I asked the user to try if he can trick Play to install the app, he did, and the app finally installed
after the installation, he got a new error message, "Missing shared library", so he still couldn't run the app
after some research, I found that some device may not have proper Google Maps api, or something like that, but it can be fixed by adding Google Apis to the apk, by explicitly adding Google Api to the Build path
I sent him the newly compiled apk, the new error message is: "Application not installed"
the user has problem with more apps, not just mine, typically with apps that uses GPS, and I guess Google Maps too, so it may be a device fault
as a side-note, I am using standard MapActivity, not the ActionbarSherlock mapactivity, but since the problem is there for the old, non-holo version of the app too, it shouldn't matter
Is there any way for me, to solve the issue on my end? I dont really care, if he still won't be able to run another apps, if he can use mine. Of course, if all his problems would be solved, that is the best case, but my priority is, can I add something to my apk? Or, what is the problem here? A corrupted Google Maps?
Thanks in advance, cheers
after the installation, he got a new error message, "Missing shared library", so he still couldn't run the app
This will come from some <uses-library> element in your manifest.
but it can be fixed by adding Google Apis to the apk, by explicitly adding Google Api to the Build path
Um, no, that will not work.
Is there any way for me, to solve the issue on my end?
Other than by switching to something like OpenStreetMap, no.
A corrupted Google Maps?
More likely it is a device (or ROM mod) that has pirated versions of various Google apps, such as Google Maps, and therefore did not set up the Maps SDK add-on properly.