I'm pretty sure that i'm using Inapp-billing v3 in my app ("IInAppBillingService.aidl" is v3 as far as i know - "IMarketBillingService.aidl" would be v2 according to the google-documentation).
however, i received an email from google asking me to update my app from v2 to v3 as at least one purchase was made using the old API in the past 3 months.
Also - i never had V2 implemented in my app so an old version should not be the case.
Is this a mistake by google, or was one of my uses purchasing something using a old play-store, so some kind of support/compatibility-mode was activated?
Or am i mistaking and i'm really using v2 of the api??
how can i find out (for sure)which version i have implemented?
this may be a stupid question, however, the email from google confused me...
I got the same email as well and am confused by it.
I also use IInAppBillingService.aidl and within IABHelper there's a method launchPurchaseFlow which calls getBuyIntent with the first parameter being version, which is set to 3 so I'm pretty certain I'm using v3.
The IABHelper I'm using is littered with v3 checks and comments.
Suggest you check the same piece of code to make sure and put it down to a Google error otherwise.
Related
I'm just coming to the end of writing my first game, last thing to do is enable backing up the user's game. I have leaderboards and achievements implemented fine, and all Google's docs say I should be saving games to Drive using .requestScopes(Drive.SCOPE_APPFOLDER) which upon trying leads me to find that it's no longer going to work in 2 months.
Digging further, I found this line from Google: "Support for storing and syncing in the app data folder will likely be removed from Drive in the future."
I'm still learning all this as I go, and I'm using Kotlin (I don't know Java). Can anyone point me in the right direction to where I should be looking to backup users game data if the way Google suggests isn't going to work very soon?
Thanks
Google is deprecating the Google Drive Android API in favor of the Google Drive REST API. Here is the best starting point for implementing that in android that I could find.
Now I was taking app list and app details from Google Play.
It's based on open source below.
https://code.google.com/p/android-market-api/.
Actually it worked well before a week but now all APIs in source code above are blocked.
I investigated source code and found "https:// www.google.com/accounts/ClientLogin", one of APIs returns "https:// developers.google.com/identity/protocols/AuthForInstalledApps".
Because of this result, http:// android.clients.google.com/market/api/ApiRequest in android-market-api cannot be used anymore.
Message
Message says I have to migrate to OAuth 2.0 but there is no API for the same functions above.
Here is my questions.
Is there official APIs with OAuth 2.0 for the same function above ?
Is there alternative APIs or process for the same function above? (The best is finding a way to use android-market-api.)
I really have to resolve this issue. Please help me.
Thanks.
I'm currently using Google maps API and directions API for getting routes, however there is a limitation upto 2500 requests per day. so while searching for a way, got confused after i came across this link..
Google Maps Mobile SDK for Business: Android
Can anyone please explain the difference between this sdk and google maps API..?
its basically a software development kit that makes use of the google maps api and helps you in development of apps that use those apis... if request limitation is an issue try other opensource apis like argcis or tomtom etc
In order to use the individual SDK such as map, you would require a key. That key is persistent, meaning once you have one, you can keep using that same key in your app manifest, regardless of how many copies of the same app you have.
However, there is a daily limit imposed on how much keys can be requested per day from google to prevent abuse. With that said, I don't think you would have a problem of requesting one. If it is given out for today, just wait till tomorrow and the limit would be refreshed.
As for the Enterprise version, you get more support over the normal version. The main differences is that you get the Business SDK as a static library rather than one using the Google Play Services. That is all.
I'm really hoping someone can help me. I'm using google maps in an application. I am working on someone elses code so I'm not sure how to fix this problem. The code checks to see if textureview is supported, if it is use it else use surface view. The maps work perfectly with newer devices, however, when testing it on a htc desire 2.2.2, there are no maps displayed. It actually says in the logcat authentication error, I'm not sure how this is possible because there isn't any authentication error when running on newer devices.
The code used is from this library
https://github.com/NyxDigital/NiceSupportMapFragment/blob/master/src/com/NYXDigital/NiceSupportMapFragment.java
In the services section of the Google API's console Google Maps Android API v2 only is set on.
The authentication error I think is unusual as there isn't an issue with the newer devices.
If anyone has come across this before I'd appreciate it you could offer some advice
EDIT ---- THIS PHONE IS RUNNING 2.2.2
This may be a duplicate issue of some other API V2 authentication error questions questions please see:
Android Google Maps V2 authentication error
and
Google Maps API V2 - always get authentication error
For anyone that might come across this issue in future...
This line
holder.setFormat(PixelFormat.RGB_888);
of the git hub library code was preventing the map from being displayed, it wasn't anything to do with authorization. The authorization issue was that I wasn't using the correct debug key, but when I had sorted this issue, the maps not displaying was still causing hassle.
So after much debugging and commenting of code, I discovered that the above line is the culprit. So I added a simple check and it's sorted
Does anyone know how to make a simple app in android dev eclipse with a simple in app purchase item like 50 coins for 0.50p in android because there are absolutely no tutorials out there and the android in app billing example isn't exactly helpful.
The current version of Android In App Purchase is V3
http://blog.blundellapps.com/simple-inapp-billing-payment-v3/
My blog post is titled Simple In App Purchase v2, so that might help:
http://blog.blundellapps.com/simple-inapp-billing-payment/
I've also recently written an overview with a flowchart to try and explain InApp Purchase (not so simple):
http://blog.blundellapps.com/overview-of-android-in-app-billing-flowchart/ (v2)
Does this library (AndroidBillingLibrary) solve your problem?
Attention!
Here is answer for IAB v2
And you, most likely, looking for v3 (which is much simpler)
Don't get in this trap, as I did...
Google I/O 2013 - In-App Billing Version 3 - http://www.youtube.com/watch?v=DgcJPIRpfSk
You can check example with library for inn app billing.
Example