The latest update to the Google Play Services Library of the Android SDK removed the LocationClient class from it. How can i downgrade to the previous version so i won't have to rewrite the code to retrieve a client's location?
I do intend to change the code to use the new LocationApi later, but for now, i need a quick fix.
Go to settings>apps>all and find Google Play Services. Tap it, then tap 'disable' or whatever it is. Then tap on the 'uninstall updates'. After you've installed your version of the services, remember to tap the button 'Take to use' or whatever is displayed.
I found this site here which has links to mirrors of Android SDK Extras by Google. I downloaded google play services SDK r21 from there and am currently using it.
http://venomvendor.blogspot.com/2012/03/android-sdk-extras-by-google-inc.html
Hope this helps someone.
Related
I am trying to add Google Play Services in my application in the Xamarin.Android platform as follows. However, it seems there is something wrong!
Here are the steps that I followed:
Step 1 : In the components -> Install Google Play Services - Maps
Step 2: Once the installation is completed, it shows as follows
When I click on the component, it shows as follows:
Step 3: After I get the above error, then I added GooglePlayServices.Maps.dll in the References, but still the incomplete message exist.
I know this answer is coming a bit too late but it could help someone.
The solution is really simple. Just use 29.0.0.2 version of Google Play Services - Maps (not the latest one).
Hope this helps.
I'm building a simple android app that uses Google maps api to display map and navigation. As you may know Google maps need Play services Library to run on client android phone. i want my app to run in much older android OS's(14,15,..)
Problems:
1- Clients need to install or activate Play services app.
2- then Clients have to update play services app to the latest version to use my app with google maps.
3- how to make app to run in older androids? just by specifying min sdk ?
so in order to solve first and third problem i've no idea but for the second one :
building project with older Play service dependencies may help but i dont know how to do this or even it helps or not.
it'll appreciate if guys offer any solutions !
Thank you all.
What are the recommended practices for maintaining the widest backwards compatibility of an Android app while depending on Google Play Services?
Here are the pointers I was able to aggregate concerning backwards compatibility, including those that use Google Play Services.
The Google Maps Android API uses OpenGL ES version 2 to render the map. The least Android API version that has support for this is API 8 or Android 2.2 .
Compile against the oldest version of Google Play Services that contains the APIs that you need. As further discussed in this thread, refrain from using wildcards like 5.+ because that updates to the latest play services. Instead use a widely used version like com.google.android.gms:play-services:5.0.89.
Use the V4 support library to verify and request permissions.
com.android.support:support-v4:23.0.1
You might also check some additional insight from this SO thread.
I'd like to implement banner-ads in my new app and stumbled across two possibilitys of doing this.
The first one is using the Android SDK: com.google.ads.*
The second one is using Google Play Services: com.google.android.gms.ads.*
I googled a lot and read the documentation but I found no resources which state the differences between both solutions.
What is the difference between both and which one is the best if I simply want to add banner-ads in my app?
Direct to the point,
The main difference is that if you use Google Play Services one then you will use Google play service APIs. If you use other modules of Google Play like maps, location, gcm, play games then you can use com.google.android.gms.ads.* but if you don't use other Services then use com.google.ads.*
Their behavior is same...
As Selvin did not post his comment as an answer I'll answer this question by myself:
Use the Google Play Services com.google.android.gms.ads.*
Don't use the Android SDK for Ads because it is deprecated:
Deprecated. On August 1, 2014, Google Play will stop accepting new or
updated apps that use the old standalone Google Mobile Ads SDK v6.4.1
or lower. You must upgrade to the Google Play version of the Mobile
Ads SDK by then.
Google Mobile Ads SDK
I am building an application which has its major functionality on google maps. But the problem I am facing in one of the device is that:
The Google Maps never load on that device [its OS is Android v2.2]
I have checked for the Google Play Service and it always gives a dialog to update the Google Play service; but when I click ok it redirects me to the play store where it shows that i already have the google play library [No update option there]
I connected the device and checked the logcat which states something like this:
"Current Google Play Service Version is 35xxx and required is 41xxx"
but there is No way for me to update the google play service as it never shows the update option. Please help me with this issue.
Give me all possible solution that i should try out... I need this app working on android 2.2.
I am using google maps api v2. Also Note the app is working fine on all other android versions.
Thanks.
USING Google Maps v1 can SOLVE MY PROBLEM....?? Please Help!
You need to use older version of Google Maps Android API v2.
The latest supported on 2.2 devices is 3.2.65 (v12) and can be downloaded via SDK Manager.
Just look for Google Play services for Froyo.
Or if you are using Android Studio and Gradle, make your dependency version equal to 3.2.65.
I want to implement the new Google Play location services api in my app, but my app must run on older phones as well, even the ones with limited space and without the play services installed. How can I set up a fallback if the GPLS is not installed? I tried moving the location listener over to another class, but that wouldn't work. I hope some of you can help me.
Thanks,
You could always use a support library that supports backward compatibility. And if that fails, you can always fall back on the framework APIs. In your case, that would be Location APIs
HTH