More than one week ago I deployed version 1.0 of my apk on Google Play - no problems. On January 6th, I deployed version 1.1. After Google Play had updated the apk for public, I got the update trigger both on my Android tab and on my smartphone. Unfortunately there was a bug in the last version, so I updated again to version 1.1.1 on Janurary 7th and deployed it on Google Play. It's already provided to public. This usually takes about 1 - 2 hours. If one downloads the app, he gets version 1.1.1. I already tested that. But since the latest update, both my smartphone and my tab doesn't get the update trigger anymore. So they don't know that there is an update again. The deployment was 12 hours ago, so there must be the trigger by now. With the update on version 1.1, I didn't have problems and I got the trigger as soon as Google Play updated the apk for public.
Any ideas why the update trigger doesn't work and both Android 3.1 tablet and on Android 2.1 smartphone? I guess it's a Google Play or apk issue since it doesn't work on both devices.
(The version name and number in AndroidManifest have been incremented. Otherwise I wouldn't be able to update the apk on Google Play)
What I noticed: Google Play haven't updated the statistics for my app since Jan. 6th although it should update daily (and it worked until 2 days ago). Maybe it's based on the same issue.
I think I know what's going on, but I can't definitely say if this is really so. Google changed something in Google Play (like recently the concept of some implementation issues like Google Play Services instead of MapView), so I think that Android versions beyond Android 2.2 and above are already too old for the last changes (They cannot even use Google Play Services). Maybe that's the reason why it doesn't work. On my Android 3.1 tablet it obviously works again. At this one time as it didn't work, there was maybe a bug in Google Play.
It this is wrong, plz correct me.
Related
I'm facing the same issue as in Stack Overflow question "Google Play services are updating" in Google Maps API.
Unfortunately, out of nowhere, some of my users are suffering this issue, as well as my own phone. On the other hand, for other users it seems to work perfectly fine.
This issue appears only on maps in my app.
I've tried to clean Google Services's cache on my own phone - still nothing.
On my emulator it works fine.
I've searched all over the Internet and haven't managed to find a working solution for this.
The most important part is this: Most of the solutions that I've found were ones that needed to be done on a specific device, like cleaning a cache and then restarting the phone. But, when we are talking about an issue that occurs and harm a large portion of my users - there has to be a solution on which I can use in order to help them all at once, by myself, without them needing to do some actions on their own phones.
Otherwise, it would be very frustrating for them, and it would make some of them uninstall my app, and because of what? A bug that I have nothing to do with? Everything worked just perfectly fine until about two days ago, and I didn't make any changes to my app since then at all... so... why?
This bug is reported by many people in the Google issue tracker. It looks like a wide range of Huawei devices is severely impacted by the latest Play Services update to version 12.6.73. Apparently something changed on the Google side and they are currently investigating what is happening.
The issue is tracked in the following bug:
Authorization Failure in Google Maps Android API v2 (Google Play Services 12.6.73, Huawei devices)
Star the bug and follow messages from Google engineers.
UPDATE 2018-05-15
Some messages from the bug
Have just got off the phone to Google and Huawei. Huawei seem to be
admitting responsibility. They told me there is an EMUI update due in 1 to
2 weeks that should fix "all google maps issues".
Also ah...#google.com states
Google has been able to reproduce the problem on a physical device and is now focusing on addressing the root cause through either a fix or other mitigation.
It looks like Google and Huawei have to look into this issue together in order to provide a permanent solution.
UPDATE 2018-05-16
Google posted the following message in the bug
In collaboration with Huawei, Google engineers have identified the root cause of this issue as an unexpected change to the filesystem permissions. The issue can impact any Android app on a Huawei device which renders a Google map.
Our engineers are preparing a new version of Google Play Services which should resolve the problem. It will be targeted to devices running Android 7.0 Nougat, or higher. We will post another update with the status of the rollout.
Thanks for your patience.
UPDATE 2018-05-17
Finally good news from Google
We are pleased to report that a beta version of Google Play Services is ready. We believe this version mitigates the issue on Huawei devices running Android 7.0 Nougat, or higher. An important caveat is that each time the device is rebooted, you will need to wait about one minute before launching the affected applications.
Starting today at midnight (Pacific Time), the beta will be rolled-out to a segment of the community that has signed-up for the Google Play Services Public Beta Program. It will ramp to increasing segments of the beta audience over the next few days. We invite you to join the beta program at https://developers.google.com/android/guides/beta-program to obtain an early release of this and future versions of Google Play Services. Once beta testing is complete it will be rolled out in stages to all users.
UPDATE 2018-05-18
As a follow-up to our last update (comment#342), we believe this issue is fixed in Google Play Services version 12.6.85. If you are still encountering the problem, please ensure your device has this version installed.
As previously noted, there can be a delay (usually less than one minute) between the time the OS is finished booting and Google Play Services starts. If you launch one of the affected apps during this window, it may not render a map. If this happens, re-launch the app after a minute or so. Subsequent launches of the app should succeed every time.
FINAL UPDATE 2018-05-22
As of 10:00 AM (PDT) on May 21, 2018, Google Play Services version 12.6.85 was pushed to 100%, following the initial beta rollout. We believe this resolves the Google Play Services issue on all impacted Huawei devices.
Huawei is working on a longer term solution which is beneficial to its users and developers.
We apologize for this incident and the impact it may have caused. We are conducting an internal investigation of this issue and will make appropriate improvements to our systems to help prevent future recurrence. Stay tuned for an Incident Report.
AFAICT there is nothing an app developer can do to fix it. As #xomena mentions in her answer Google is working on it.
Just to add the complete solution for an end-user here:
go to Settings > Apps & Notifications > App > Google Play Services > Storage
click Clear Cache
go to Manage Space and click Clear all data
Be aware that the issue reappears if you reboot your device
Someone created a video you can refer your users to at https://youtu.be/VgMtZnyem5Y
It's is going to be fixed soon, guys:
https://issuetracker.google.com/issues/79405933
Go to Settings → App → Google Play Services, and disable it to go back to the factory version.
Restart the phone and go to Google Play Store to do the update on Google Play Services.
It works for me. I can see the Google map again in a third-party app. If it says uninstall/disable, do that.
There is nothing you can do at this time, except clear Google Play Service data (without rebooting the phone). At the next reboot, maps services get updated, and the issue will be there again.
We just can wait for Google to fix it with a mitigation update, and Huawei give users new firmware via OTA that better comply with the last Google API without what seems like an "authorization" issue.
Today Google released version 12.6.85 on the beta channel which fixes the map bug.
You can suggest your user to subscribe as a beta tester:
https://play.google.com/apps/testing/com.google.android.gms
Or direct download on APK mirror:
https://www.apkmirror.com/apk/google-inc/google-play-services/google-play-services-12-6-85-release/google-play-services-12-6-85-040408-197041431-android-apk-download/
I tried disabling to restore to the factory version - unfortunately this means most of my apps required Play Services will not run, and I can't seem to reinstall the latest version.
I am using Honor 7x.
As the title says, we published a new version of an app 2 weeks ago. Play Store indicates in the registry that the new version was uploaded (1.7), and allows it to be downloaded to users who did not have it. Not so, for those who already have it, for example, users who have version 1.6, do not see the option to update, just uninstall or open.
We expected it to be only a matter of time, but 2 weeks is already too much. We contacted Google support, and they only ask us questions like: "Have automatic updates for the application enabled?" ... Does anyone know what is happening, or if it is our mistake, some step wrongly made? We generate the apk directly from Android Studio and change the version.
One of the issues that your users might have is this
Maybe they disabled the auto-updates of Google Play, but is really weird that they can't see it, maybe it's due the devices. Is your device listed as compatible with the new version of your app? Did you tried clearing Google Play cache and trying it again?
PS: Make sure you change in your Gradle (Module app) your versionCode along with the VersionName
If new users are getting the new version installed then it is definitely uploaded to the Play store correctly.
If existing users aren't seeing "update" (just open) then it means there is something about the new version of the app that is incompatible with their devices. You can check this by trying uninstalling and re-installing. If they get the old version after an uninstall / re-install (or worse, if they can't install after uninstalling) it shows that only the old version is compatible with their device.
This probably means you changed something in the manifest to make it incompatible, but that is a whole different debugging problem.
When my personal phone upgraded to Marshmallow (6.0.1), my app became no longer visible in Google Play.
The manifest has:
Minimum SDK: 10
Target SDK: 22
No maximum SDK
I tried uploading a test app with everything the same except with Target SDK = 24, and it did show up in Google Play.
While I could upgrade the app for Marshmallow, I would rather not have to.
What is going on and can I do anything about it?
Im might be wrong, however, I believe you have to update your manifest and upload the apk again.
Basically, your current manifest is targeting devices with android version from 10 to 22.
You have to change your manifest and set target SDK to 23.
This is expected since your app may not work well in android MM.
You are responsible to update the manifest, test and only after that, upload the new version to Google Play store.
Now I feel really dumb, and not to happy with the Play Store search algorithm!
The app is still visible. But, even though I searched for it by the starting two words of its name, it was so far down in the play listings that I didn't see it. This is an app with over 10,000 installs and a rating around 4.5 and current sales.
So, if you don't see you app in the play store on a device, scroll all the way through the category, or put in the entire name.
I'm using Google Cloud messaging through google play services. The things is it only works on the devices with last version of play services installed, in remaining devices i need to show a dialog to send user to google play to install new version witch i really don't want to do!
So how can i avoid this?! I'm trying to use an older version of play services (lets say from 2 years ago) to insure majority of my users don't need to update but it seems impossible with grade and android sdk since it already deleted older versions! So what should i do? Is there any way to use older versions?! and if do find a way to use an older version are newer versions compatible with older one?
I don't want to force my users to update because
GCM it's not essential to my app although i like to have it!
It's over 30 MB witch is a lot in third world countries were my users are.
Google play blocks some of my users from accessing google play due to international lows! and i have to do update manually my self!
There is a solution for android studio:
1.Close your project
2.Browse to the folder where your projects has been saved
3.Go to folder 'app' and open the file 'build.gradle'
find this line :
compile 'com.google.android.gms:play-services:7.3.0'
and change the version (here 7.3.0) to an older one (like 6.5.87).
You can find out available versions by looking at sdk/extras/google/m2repository/com/google/android/gms/play-services
5.open the project again
Unfortunately Google Cloud Messaging was only added to the Play Services API in version 7.5, which was released end of May 2015 (see this Android Developers Blog post).
So, if you manage to find a copy of the v7.5 API (see my question regarding that here) or if the suggestion above by #Babak is safe (still investigating that one... and you can only go down to 7.5.0 before you lose GCM support), you might be able to gain a few months, but it will likely not make a huge difference...
Actually, I just noticed that your question was also posted end of May... So you probably won't be able to gain anything. But you may reduce support of you move to a new API version later!
Say I have an application that users have installed from the Play Store, if one of my users reports a bug and I want to send them a patched version of the app to test, they can install it to their phone just fine. But if I then update the app on the Play Store, will the user get the update? My testing seems to indicate this is the case, but is there any gotchas?
The way my build process works is that each time I build, it gets a higher version code, so the patched version will have a higher version code that the one currently in the Play Store and then the version I upload to the Play Store after sending my user the patch will have a higher version code again.
I'm taking a decently wild guess here, but it should work, provided the following are met:
The version code of the apk on Google Play is higher than that of the hotfix
The user originally installed the app from Google Play to begin with, and only updated it via side loading.
The hotfix and the Google Play update are both signed with the same key.
I'm decently sure this will work, as I recall a long discussion about this on one of the android google groups that ended with success. I unfortunately cannot find it right now.
If you do try it out, please post back with the results.
I don't see any issue with this workflow. As long as you increment the version number at each build.