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.
Related
I can see the PayPal Mobile SDK requirements say it needs Android 2.2 or later, https://github.com/paypal/PayPal-Android-SDK#requirements. And the Kindle runs a customised version of Android 4. So it should work, but I haven't found any mention of this combination.
The mobile SDK should work on the Kindle. If you have a Kindle device, you can test it for yourself.
I'm thinking of use this to interact with G+ circles:
https://developers.google.com/+/mobile/android/getting-started
The question is, does it works in Android devices 4.1 or later?
Cause in the "get started" page says in prerequisites: A physical device to use for developing and testing because Google Play services can only be installed on an emulator with an AVD that runs Google APIs platform based on Android 4.2.2 or higher.
This apply only to AVD, right?
Google Play Services supports Android devices running Android 2.3+ and emulated devices running Android 4.2.2+.
https://developer.android.com/google/play-services/setup.html
I published an app to Google Play, but some of my users are unable to find it using their device.
The min apk for the app is 11 (Android 3.0).
When someone uses for example a Samsung Galaxy SII with Android 4.0, the app can't be found because the initial release of the SII was with Android 2.3. With a SIII it's no problem.
In the developer console, the console automatically checks to see which devices are compatible when uploading the apk. As developer, I can disable devices for download, but not enable devices.
Does Google Play check the current version on the device or does it uses the versio, of initial release?
How can I reach as many as possible devices? When I lower my min APK in the manifest, I get compilation errors.
Thanks in advance
That's a really good question. Lowering your minSdkVersion or publishing multiple APKs is the best solution to reach many devices, your problem with this approach is that probably you are using some API features that aren't present in older APIs so that's why you're having compilation problems.
http://developer.android.com/google/play/filters.html#manifest-filters says:
Example:
The manifest includes uses-sdk android:minSdkVersion="3", and the
app uses APIs that were introduced in API Level 3. A user is searching
for apps on a device that has API Level 2. Result: Google Play will
not show the app to the user.
So I assume google will filter based on the current API version.
Can you post your app link?
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 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.