After changing the Play Service version, and installing on my phone, android studio gave me a warning saying that I can't update the existing application, and I must uninstall it.
its give you warning because in you device you have signed APK and you are trying to update it using debug apk. so generate signed apk(with same certificate whatever you have used previously) then update app in device.
So, can I still release the new APK in the developer console, and will it cause issues?
in above process there is no issue then you can upload same signed apk on Google Play Store
assume you know what is signed & debug apk and how to generate both
EDITED:
Gradle is a build system. i am not able to explain it in simple way but you can read more detail of Gradle in this answer and for more about build system and Build System Overview
Answer from Dhaval Parmar on Stack OverflowRecently I reset my ONE M7 and I found that Play Services can't be Updated .Do anyone know how to fix this.. on Play Store it won't show any update button.. I never Saw these Things in my Other 2013 phones like Galaxy S4.
Videos
What is Google Play Services?
Why is it important to keep Google Play Services updated?
Can I uninstall Google Play Services?
After changing the Play Service version, and installing on my phone, android studio gave me a warning saying that I can't update the existing application, and I must uninstall it.
its give you warning because in you device you have signed APK and you are trying to update it using debug apk. so generate signed apk(with same certificate whatever you have used previously) then update app in device.
So, can I still release the new APK in the developer console, and will it cause issues?
in above process there is no issue then you can upload same signed apk on Google Play Store
assume you know what is signed & debug apk and how to generate both
EDITED:
Gradle is a build system. i am not able to explain it in simple way but you can read more detail of Gradle in this answer and for more about build system and Build System Overview
I suspect that what happened here is that your signing key doesn't match. (I.E. if you downloaded your release-key version from the Play store while using the debug key with Android Studio) Changing Play Services should not have this impact.
Settings > Apps > Google Play Services > Notification settings > off
Settings > Apps > Google Play Store > Notification settings > off
That's it.
Each time I have reset my phone, exactly the same thing happens. I cannot update individually only Google Play Services as it goes into an infinite loop of popups saying that you cannot Update until you Update.
The solution which worked every time is to go to the Google Play Store into the Apps and Games (sometimes called differently depending on the version) and doing a Update All. Obviously, it may update more than you want but that is the only reliable way that worked on Android 7.0. Hopefully, this can work (or some similar steps) for your version too.
Normally only take a second for it to show if is there's an update, but since yesterday been stuck on "Checking for update". I tried clear Google play services cache & rebooted the phone and it still stuck.
Update: Finally all my devices are no longer stuck and all updated to November 1 update. So just wait patiently and it should solve the problem itself. (OnePlus 6T, 7T, N10, RedMagic 7 Pro, 8S Pro)
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 [email protected] 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 Spaceand clickClear 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
Update On 18-Dec-2017
You can update Google Play Services via the Play Store app in your emulator just as you would on a physical Android device from API 24.
check Emulator new features added with stable update from Android Studio v 3.0
Google Play Support - From Google : We know that many app developers use Google Play Services, and it can be difficult to keep the service up to date in the Android Emulator system images. To solve this problem, we now offer versions of Android System Images that include the Play Store app. The Google Play images are available starting with Android Nougat (API 24). With these new emulator images, you can update Google Play Services via the Play Store app in your emulator just as you would on a physical Android device. Plus, you can now test end-to-end install, update, and purchase flows with the Google Play Store.
Quick Boot - Quick Boot allows you to resume your Android Emulator session in under 6 seconds
Android CTS Compatibility
Performance Improvements - With the latest versions of the Android Emulator, we now allocate RAM on demand, instead of allocating and pinning the memory to the max RAM size defined in your AVD.
Virtual sensors
Wi-Fi support
GPS location and Many more...
OR
Update this SDK Build-Tools and Android Emulator to latest and this alert message will not come again,
Settings --> Android SDK --> SDK Tools(tab) --> Android SDK Build-Tools
Use/ emulate a system-image that has "Play Store" pre-installed, those with "Google Play" in targets column (instead of Google APIs). Updating play services would be as easy as in real device.
Since Google introduced Google Play Store images in Android SDK Tools 26.0.0 now emulators comes with installed Google Play Store.
From 26.0.3
- Adds a new tab in the extended window for Google Play Store images that displays the Play Services version and a button to check for updates to Play Services.
But even with all above (last checked 2022), you can NOT use the Emulator to test Google Play Billing:
- You must install your application on a real device to test Google Play Billing,
- Or, ask Google for "closed testing" permission.
see How to test In-app Billing on an emulator?