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.
Related
I have an Ionic (Angular) application published on Google Play, however it has 2700 compatible devices and I am having problems, because several users are unable to install or update it anymore.
I looked in forums and on the Google Play Console support page, and the only things I found about it is talking about the Minimum SDK Target and settings in the AndroidManifest.xml for functions and mandatory sensors. However, my app does not have any mandatory functions or sensors configured in the AndroidManifest.xml and my Minimum SDK Target is 19 (4.4).
Has anyone been through this and knows how to solve it? Because I have other apps using Ionic as well and React Native that compatible devices reach 17 thousand
First of all: I am a Software Testing Engineer, so I don't create applications. I use Android Studio for AVD creation, than I install already developed apk file on Android Emulator and make tests. About a month ago I have noticed an annoying pop-up "Update Google Play services" and when I clicked "Update" button - nothing happened.
I don't want to describe all my struggles, but finally I decided that root cause is the outdated Google Play Services SDK (now I have version 38). Android Studio doesn't offers me to update it, and also I can't find any information about version 39. Maybe you know something about this and can help me?
You can always check here the latest version of Google Play service. This is the official documentation of Google Play service that shows you the update and the highlights of each version. This page also shows you how to use the Google Play services APIs in the Android studio.
Note that to test your app using the Google Play services SDK, you must use either:
A compatible Android device that runs Android 2.3 or higher and includes Google Play Store.
The Android emulator with an AVD that runs the Google APIs platform based on Android 4.2.2 or higher.
I have an andengine game project where I am using Google leaderboard. Previously I was using Eclipse and older version Google-play-services. Now I have migrated to Android studio and using the latest version of play-services. But whenever i run the app on different different devices these are the results I get...
Case 1) If the device doesn't have the game-play-services app
App won't run unless you have play-services installed (get
play-services option)
Case 2) If the device have older version of play-services
App won't run unless you update the play-services (update
play-services option)
So my app totally become dependent on play-sevices app which I definitely don't like and many of my users hate it. Is there a way to basically integrate Google leaderboard without having these strings attached?
Thanks.
No. Google Play Services allows your app to connect to given Google APIs (incl. leaderboard). Officially, there's no other access on Android than thru Google Play Services.
I have recently included android wear support in my app but when I went to publish it today I was made aware my earlier version would be archived. My earlier version was targeting api 16 to include as many devices as possible.
I was hoping if a user doesn't have the latest devices capable of running my updated android wear version then they would get the earlier version I have published.
What is the correct procedure to enable this to happen please?
Regards
It is possible to keep your app supporting API 16 while adding Android Wear support. The Google Play Services library runs on many older devices, and it will do the right thing to ensure that your code will not crash. Since an old Gingerbread phone cannot support Android Wear, you will just get an error code when you try to make use of Wear functionality, and you can just handle it gracefully with whatever way is appropriate for your application.
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.