I downloaded sample in-app-billing application and I tried to run that application on devices
its working fine for devices with android OS version 2.2.
but I am getting problem with devices having OS version 2.1.
Actually I am able to connect to market server and I am receiving response saying that request sent to server ,but I am not getting response about purchase state (ie whether the purchase is success or not).
we are getting this problem with android OS 2.1 devices,for OS 2.2 its working fine.(i tested in devices with OS 2.1 and 2.2 only)
From developer pages: http://developer.android.com/guide/google/play/billing/billing_subscriptions.html
System requirements for subscriptions
In-app purchases of subscriptions are supported only on devices that meet these minimum requirements:
Must run Android 2.2 or higher
Google Play Store app, version 3.5 or higher, must be installed
Google Play 3.5 and later versions include support for the In-app Billing v2 API or higher, which is needed to support handling of subscription products.
Related
Is it possible to use Androids Account Transfer API with a usual Android phone as source and a Wear OS smart watch as receiver? According to the documentation the setup has to look like this:
The source device must be running Android 4.0.1 (API level 14) or
higher.
The target device must be running Android 8.0 (API level 26)
or higher.
Both source and target devices must be running Google Play
services version 11.2.0 or higher. You must build your APK using
Google Play services SDK version 11.2.0 or higher.
I want to sync my phone's accounts to my smart watch.
If your objective is to sync data from your Android phone to an android wear, I think Google Fit API will do the job.
Google Fit is an open ecosystem that allows developers to upload
fitness data to a central repository where users can access their data
from different devices and apps in one location:
Fitness apps can store data from any wearable or sensor.
Fitness apps can access data created by any app.
User's fitness data is persisted when they upgrade their fitness devices.
Also, it was mentioned in the documentation that the least Android 2.3 (API level 9) and higher is supported.
Android documentation here says new Google Cloud Messaging API requires Google Play services version 3.1 or higher on the device.
What is the status of implementation of this service?
Are all android devices updated with Google Play services version 3.1 or higher?
Since Google Play Services are automatically updated on devices via Google Play, the vast majority of devices are running the latest version. It updates whenever the user connects to the internet, without user interaction.
I can't seem to find any statistics on this, but I'm fairly sure that all 2.2 and above devices will be running the latest or penultimate version.
I would like implement in-app subscription on my android app, but what's the minimum target to do that ?
2.1 or 2.2 ?
From the Android Developers site (Version 3 is the latest):
In-app Billing Version 3 is supported on devices running Android 2.2 or higher that have the latest version of the Google Play store installed (a vast majority of active devices).
So the minimum target is 2.2.
http://developer.android.com/google/play/billing/billing_overview.html
As soon as I know, the subscription "minimum target" is related to the Google Play Store app, and not from your app.
Take a look at:
http://developer.android.com/google/play/billing/versions.html#Subs
In-app Billing Version 3 is supported on devices running Android 2.2 or higher that have the latest version of the Google Play store installed.
Source: http://developer.android.com/google/play/billing/billing_overview.html#migration
Use the version 2.1 and above since for all the mobile devices are almost higher versions and its good to develop with min version 2.1 & above.
Before deciding the min version for your application you must always check the platform distribution on google. For example, I choose not to include 2.2, since it brings unnecessary API legacy issues and too much work for too less benefit. Keep in mind, in-app billing is really complex to get right. The API's are just crazy'ly complex.
I'm want to do "In-app Billing"
http://developer.android.com/guide/market/billing/billing_testing.html
on my app.
But it is not possible to test in-app billing in the emulator. So what phone to I need for testing? Is it only Android Dev Phone 2 and Nexus One that works?
"To test in-app billing in an application you must install the application on an Android-powered device. You cannot use the Android emulator to test in-app billing. The device you use for testing must run a standard version of the Android 1.6 or later platform (API level 4 or higher), and have the most current version of the Android Market application installed."
Should work on any device that has Android Market App version 2.3.4 and greater. Have written a blog for some critical issues found during setup.
http://mcondev.wordpress.com/2011/06/12/securityexception-binder-invocation-to-an-incorrect-interface/
From your quote I can't see that it is limited to a specific device. All devices running Android 1.6 or later should be possible to use in your test. Just make sure that you update the Android Market application before testing.
Any standard android device running the latest version of the Market will do. I've seen it done on an old TMobile G1.
The device you use for testing must run a standard version of the Android 1.6 or later platform (API level 4 or higher)
Taken from http://developer.android.com/guide/market/billing/billing_testing.html
I'm using a free Samsung Galaxy with Android 2.1 and works fine. So any cheap android device should work.
That's the business, isn't it?
You can use this test framework : android-test-billing to test the In-App billing on the emulator.
This framework was tested by the project Horer - les horaires de RER.
Emulator testing should complement the real device testing, so you still have to get the device for testing before the final release to the Android Market. I advice the Samsung Galaxy Mini as the cheap phone for development.
I have several questions about the Android in-app billing, as I cannot find what I need in the documentation.
1: It does require Android 1.6 or higher, AND Market 2.3 or higher. How can I install Android Market 2.3 manually, if the device I have is NOT rooted?
2: I tried it on Android 2.2 and Market version 2.2.11, but there were errors in reading Bundle responses.
3: Does it even have a chance running on emulator?
4: What do I actually have to do, to test in-app purchase? I downloaded the sample app, and compiled it, but I could not even get my static responses back (Market app 2.2.11).
5: Actually, is it LEGAL to install the Android Market 2.3 on devices with lower Api Level? Google say you need Droid 1.6 SDK, and market 2.3, but as far as I know there are no (or very few) devices with Market 2.3 that are running below 2.3 Android. Can you update your Market app?
6: (Lame) Does the Android Market Client auto update itself, when I new one is released ?
You shouldn't have to install Market 2.3.0 manually, the market app should update itself when a new version is released.
You already said it requires Market 2.3.0 so obviously it won't work on 2.2.11.
Lots of people have been running Market on the emulator, so it may work: How to install Android Market App on the emulator?
See question 2. Also even if you have Market 2.3.0 I'm not sure Google have enabled the testing phase yet. I too would like to use in app purchases but I'm not going to bother trying it for a few months.
I believe all devices will get Market 2.3.0, not just those running Android 2.3, since it's just an app and not part of the OS, but I could be wrong.
Yes.