Since updated my SDK Manager packages, my google play services hasn't been working.
This is causing my Samsung S5 Running 5.0, HTC One_M8 running 5.0.1, and my Nexus 5 running 6.0 (the Android M preview) to crash.
java.lang.IncompatibleClassChangeError: The method 'boolean com.google.android.gms.common.api.GoogleApiClient.isConnected()' was expected to be of type interface but instead was found to be of type virtual (declaration of 'java.lang.reflect.ArtMethod' appears in /system/framework/core-libart.jar)
Running the same code on Samsung Mega running 4.4.2 and a Nexus 4 running 4.4.4, I'm getting this error.
java.lang.NoSuchMethodError: com.google.android.gms.common.api.GoogleApiClient.isConnected
These errors only started happening after the latest updates from the SDK Manager, I update very regularly and my last update before I noticed the issue was on October 5, 2015.
Current SDK
Android Support Repository: 21.
Android Support Library: 23.0.1
Google Play services: 27
Android SDK Tools: 24.4
Android SDK Platform-tools: 23.0.1
Android SDK Build-tools: 23.0.1
Everything worked perfectly before the update. Is there anyway to fix this? I've spend hours trying to figure out if I screwed up something somewhere, but there have been no changes to my project that involve google play services since the last time it worked. I have confirmed with someone, using the exact same codebase as I'm using (we use git) who hasn't yet updated their SDK packages, that our code still works for him. I may have to revert my SDK tools since I cannot simply wait around for a possible fix if it is a bug. I get the update is very new but I can't be the only one having this problem....
Any ideas on how to fix this?
Thanks!
Ok, I've found out what my issue truly was. It seamed odd that the isConnected() method in the GoogleApiClient would break while all the other static methods could be called without issue. But when you have an API update that get's announced as a "breaking change" you kind of expect things to not work anymore.
Well on Wednesday Oct 7'th I noticed another update which I've finally had a chance to test and the issue is no longer present. So it looks like this was a bug in their "breaking change". Thankfully Google got this fixed rather quickly. But it works now. So I've essentially reverted my code back to the way it was before. Cheers!
Related
I have migrated my app to the 5.0.0 version of the billing library, as it is adviced. However, I've found that it's not working properly on old devices in which the old library did work. I've tested it on Android 7 (Nougat API 24), Android 9 (Pie API 28) and Android 12 (S API 31). The only one in which it's not working it's on the Nougat one and I would like to know if it's somewhere in the documentation reported which API levels are supported and which don't.
The "error" I'm getting is SERVICE_UNAVAILABLE as response code when calling queryProductDetailsAsync.
I'm also assuming it's a sdk version issue, as I can't find other cause (the Play Store is updated, the wifi is on and my Google account logged in).
Something must be misconfigured in the phone. I tested on an Android 6 and it worked, so I tried completely restoring my Android 7. Now it works.
However, I still wonder why the old library worked and the new one didn't.
I have been trying to find some reliable solution to this but I couldn't. I have added Android 11 - S which is an Android 12 Beta image in Android SDKs as shown in the following screenshot
But when I go and try to create the Emulator device in Device Manager I don't see this API in the list
What Am I doing wrong here?
Final release planned for early 2022.
In Visual Studio you can find Android 12 here:
From document Android 12 Preview, we find that :
The Android 12 Preview program runs from February 2021 until the final
public release to AOSP and OEMs, planned for later in the year. At key
development milestones, we'll deliver updates for your development and
testing environments. Each includes SDK tools, system images,
emulators, API reference, and API diffs.
Since it's still in beta, there's definitely some instability, so for that reason, it's still not released. We need to wait patiently for the final release.
In VS2022 17.0.5, Android 12 is available as a choice in the emulators list. However, be warned. Debugging/deploying android Xamarin in VS 2022 as of this version is sloowwwwww. Anyone with any leads on that, please hit me up!
EDIT: it really was a bug in AS 3.1.1 related to D8 compiler as stated here. It's said to be fixed by now in AS 3.1.3, although I didn't check that myself.
I know it means it performing AOT compilation.
The thing is that I get a lot of reviews saying "everything was fine before the latest update, but the game is extremely slow now" from users on Android 6.0 and above. Some users report that sometimes the game can not respond to their actions for literally minutes.
Also, a few reviews said that the game is a cause their phones reboot takes a very long time saying it's "optimizing apps 1/1" and that the issue goes away when they uninstall my game from the device.
I cannot reproduce the issues on any devices I have on hand (I have no Android 6.0 unfortunately, only 5.1 phone and 7.1 tablet - the game runs smoothly on those)
I need help to figure out the cause of the problem.
What I did before the latest update (that caused the problem):
switched from AS 3.0 to 3.1 (and updated project to use a newer version of gradle - 4.4)
updated android support libraries to 26.0.1
updated Appodeal libraries to 2.1.11
updated libgdx version from 1.9.5 to 1.9.6
Also, I made a few minor changes in the game's core code, but I see no way of them causing system-wide issues, it has to be something of the above. Are there any knows issues with these versions of libraries?
I have a project that is completely working on android lollipop but when I build my project in Nougat version it seems not working properly.
the process of my game is when the puzzle is finished or completed a modal will appear the way I did it is I move the game object to the last sibling like this gameObject.transform.SetAsLastSibling();. Its working completely on android lollipop but not in Nougat. Any Ideas what went wrong?
ps. my unity version is 5.6.2f1
Lollipop and Nougat operate slightly differently. Seeing as that line of code doesn't do anything platform specific, I'd be one to guess that answer lies elsewhere (Unless this is a bug).
Make sure your android JDK is up to date.
Make sure the correct platforms have been installed in your SDK manager.
Completely uninstall the app, clean, build and try again.
If your app is using permissions then in Nougat you must request these at run time.
Links:
https://docs.unity3d.com/Manual/android-GettingStarted.html
i followed all the instructions in link.But after that when i started one project and try to run on emulator then it is displaying to update "This app wont run successfully unless you update google play services" and provided a update button and then when i am clicking the app is crashing.
In case of running in a device having 2.3.6 version in it, it throwing an exception and log is below:
Java.lang.ClassNotFoundException:android.view.fragementin loader dalvik.system.Pathclassloader
. can anyone help here ?
Seems that you are trying to use fragments on a device that doesn't support this (without the support library).
There is one sentence in the link you gave:
Please note that the code below is only useful for testing your settings in an application targeting Android API 12 or later
But your 2.3.x (cannot find a 2.3.6 version number in the official documentation) is maximum API level 9.
Regarding the emulator: It doesn't run in emulator out-of-the-box. It is a bit tricky but there are some guys who got it working.
Android tools --> Add Support libraries should solve the issue.