Hi guys,

1) Google announced yesterday that the in-app billing is officially
available.  However, seems I am still getting
RESULT_BILLING_UNAVAILABLE with Market 2.3.4

Then I looked at http://market.android.com/support/bin/answer.py?answer=1050566

It stated that at this time it is available only on Android 3.0
devices with MyApps 5.0.12 or higher. (This statement is only there).
NIce. Does anyone has other results with 2.3.4 or eventually has some
information when we can use in-app purchase for 2.3.4?

2) On 3.0 / MyApps 5.0.12, my test implementation of in-app purchase
works fine with the  reserved product IDs for testing static in-app
billing responses. Here is the test environment :
- I have uploaded draft apk with <uses-permission
android:name="com.android.vending.BILLING" />, signed for production
(not debug)
- The previous version of the app is published
- I created in-app items for the app and their status is published
- I created a test google user
- the testing tablet is reset and booted up with the same test google
account as primary google account

So if the sku inside in the app is one of the reserved ids (like
"android.test.purchased" ), everything is fine. If I change only the
sku to one of mine in-app items ids, and try the purchase, the market
is showing the following message window :
"Application Error : This version of the application is not configured
for Market Billing. Check the help center for more information."
There is nothing special in the log :

BillingService RequestPurchase
BillingService request id: 5088870391717748441
mPayloadcontents  null

I double checked the public key. Does anone has a better luck with
that?

Thanks!





-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Reply via email to