Finally after some days challenges I can run the GoogleMapAndroid api version 2 on the monodroid by this link: https://github.com/xamarin/monodroid-samples/tree/master/MapsAndLocationDemo_v2
but when I start this this demo face with this error:
Google Play services out of date. Requires 3027100 but found 2012110
I want that my app be available on android 2.2 and upper. On the android 2.2 by default the google play services even is less than 2012110 what should I do to support 2.2 and upper?
Thanks in advance
Go to https://play.google.com/store/apps/details?id=com.google.android.gms from your device (or computer with the same gmail account logged on) and update it to 3.0.27.
If you can't see update for you device you may want to read last commens on this gmaps issue. I'm not sure how they do it, but my device didn't get update to 3.0.27 at first.
Edit:
Alternatively you may get an old version of google-play-services.jar (version 4 = 2.0.12 is first to have maps). This has small negative aspects: you will have some issues which are fixed in later versions, but not all of them as most are fixed in GooglePlayServices.APK and not inside jar file we add to our apps.
One thing I'm aware of is this:
http://code.google.com/p/gmaps-api-issues/issues/detail?id=4862 (see comment from Googler).
You will also not be able to create Circles, but that's not problematic for most apps.
Most of the time you don't want to use old version of jar and do checks like isGooglePlayServicesAvailable inside your app.
Related
I'm trying to update my app to the Google Play Store. I have the current version number of the app set to 2000000000 and would like to update it to 2000000001. Please don't ask my why there are such version numbers chosen.
I got this error message when I try to push the new version: "Upload failed
The version code of your APK is high and you risk not being able to update your APK.". The one thing I don't understand is that according to official google documentations the max version number is MAXINT, 2147483647, so I still have roughly 150 000 000 versions left. The other thing is, I managed to update other app with the same version numbering convention, the app is on the same dev account and I have no such error at all.
I checked all the numbers couple of times to be sure I'm not doing some stupid typo. I also already contacted Google support but maybe someone here have some kind of solution?
Google support responded to my requests. They changed the maximum available version code to 2000000000 and didn't update the documentation at the time I was posting this question (right now it is still MAXINT: 2147483647). Quite an edge case here but maybe someone will find this useful.
Looks like there was an update 08/11/2016 (UTC) in the docs. Not the old MAX_INT value or the 2000000000.
Warning: The greatest value Google Play allows for versionCode is 2100000000.
My Unity app had a high version code (not sure where from), I added version 3 and version code 3 in the Unity app, and that shut Google Play :) There is a crafty version for build.gradle though Unity 3D: What is the Android Bundle Version and Version Code and how do they relate?
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!
As per the Cast SDK Docs, to use Cast SDK in Android I need, Google Play Services Revision 15.
I dont see Rev 15 in my SDK Manager. Can anyone else see it yet? or know by when we can expect to start developing for Android with rev 15? Is there an alternative stop gap to get around the problem till Google pushes out to all SDK Managers?
Can anyone else see it yet?
No, because it is not yet available.
UPDATE: OK, now it is. Let the downloading commence!
or know by when we can expect to start developing for Android with rev 15?
On the page that you linked to, in a large yellow box, you will find:
Developing with the Google Cast Android APIs requires Google Play services 4.2, which began rolling out to devices worldwide on February 3rd. Once the update to devices is complete, the corresponding Google Play services library (revision 15) will be available for download from the Android SDK Manager.
(emphasis added for emphasis, emphatically)
Note that today is February 3rd, which means the Play Services rollout just began today.
Is there an alternative stop gap to get around the problem till Google pushes out to all SDK Managers?
You can wait patiently. Or wait impatiently, if you prefer.
I believe AllCast "speaks" the Google Cast protocol (RAMP) and does not use the API. He probably sniffed it and reversed engineer it, much like others have with the AirPlay protocol.
So, if you are motivated and good with WireShark, you can do the same! Personally, I'm holding out for the API, most impatiently.
Sorry. I still can't comment, so I have to post everything as Answers (stupid rule)
I am looking for this library too and I didn't find it yet but why Allcast has one? I installed google play services 4.2 on my phone and then i installed allcast from google play and it works very nice. So why we can't get access to this library too? It is not fair we have been waiting for long time too! And why it is available first for iphone :(
It will take couple of weeks to release as mentioned here.
So we have to wait till couple of weeks more.
Google just released it. Check the SDK manager for an updated version of Google Play services (rev15).
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.