My favorites | Sign in
Project Home Source
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 7: In-App Billing does not work on Android 1.6 and 2.1
42 people starred this issue and may be notified of changes. Back to list
Status:  Accepted
Owner:  ----


Sign in to add a comment
 
Reported by ishihata...@gmail.com, Apr 10, 2011
I tried the Dungeons sample app with many mobile phones.
The app worked correctly with Android 2.2 phone, however, it cannot work with Android 1.6 and 2.1 phone.
The result of my trial is shown below. "OK" means that the app works fine and "N/A" means I cannot buy item.

SHARP IS01 (Android 1.6) N/A
SHARP IS03 (Android 2.1) N/A
TOSHIBA IS04 (Android 2.1) N/A
SHARP IS05 (Android 2.2) OK
Pantech IS06 (Android 2.2) OK
HTC Desire (Android 2.2) OK
HTC Desire HD (Android 2.2) OK
SHARP 003SH (Android 2.2) OK
SHARP 005SH (Andoird 2.2) OK
ZTE Libero (Android 2.2) OK
Dell Streak (Android 2.2) OK
Sony-Ericsson Xperia (Android 2.1) N/A
TOSHIBA T-01C (Android 2.1) N/A

(The version of the market app was 2.3.4 in any phone.)

By using "OK" models I can buy android.test.purchased without trouble, however, I cannot buy it with "N/A" models that install Android 1.6 or 2.1.
The confirmation dialog of how to buy is displayed, but if I push "buy now" button, I am made to wait for about one minute and the approving dialog closes after it. After all, I cannot buy the item.

The sample app seems to have failed to receive IN_APP_NOTIFY intent on N/A case.
Here is the logcat message about when IN_APP_NOTIFY intent is made.

> WARN/GTalkService(1268): [DataMsgMgr] broadcast intent callback:
> result=CANCELLED forIntent { act=android.intent.action.REMOTE_INTENT
> cat=[com.android.vending.billing.IN_APP_NOTIFY] (has extras) }
> WARN/GTalkService(1268): TODO: implement reportNoReceiverError! 

Strange to say, it seems that GTalkService steals IN_APP_NOTIFY intent.
Is this a bug of the market app?

Thanks.
Apr 11, 2011
#1 kmans...@gmail.com
I can also confirm this, although my sample size is much smaller:

- Moto Milestone, 2.1u1, test purchase for android.test.purchased never completes;

Weird logcat messages:

 D/vending ( 1521): [1] BaseBuyPageActivity.onOrderResponse(): state: CART_PURCHASE response: [PurchaseResult=OK]
 D/        ( 1521): unable to unlink '/data/data/com.android.vending/cache/AVMC_PSU0FfaW5hcHA6b3JnLmttYW4uV2lmaU1hbmFnZXI6YW5kcm9pZC50ZXN0LnB1cmNoYXNlZA': No such file or directory (errno=2)
 D/        ( 1521): unable to unlink '/data/data/com.android.vending/cache/AVMC_SU0FfaW5hcHA6b3JnLmttYW4uV2lmaU1hbmFnZXI6YW5kcm9pZC50ZXN0LnB1cmNoYXNlZA': No such file or directory (errno=2)

followed by


W/GTalkService( 1364): [DataMsgMgr] broadcast intent callback: result=CANCELLED forIntent { act=android.intent.action.REMOTE_INTENT cat=[com.android.vending.billing.IN_APP_NOTIFY] (has extras) }
W/GTalkService( 1364): TODO: implement reportNoReceiverError!

- Samsung Galaxy S, 2.2, test purchase completes successfully. No weird messages in logcat.

Needless to say, both tests are using the same .apk, release signed, etc.
Apr 11, 2011
#2 nathan.s...@gmail.com
I was getting a RESPONSE_CODE but no IN_APP_NOTIFY. I had to restart my phone, then I got a bunch of IN_APP_NOTIFYs.
Apr 11, 2011
#3 kmans...@gmail.com
>>>
I was getting a RESPONSE_CODE but no IN_APP_NOTIFY. I had to restart my phone, then I got a bunch of IN_APP_NOTIFYs.
<<<

Just tried it with my Motorola Milestone 2.1u1: it didn't fix anything. Still getting those weird messages in logcat (unable to unlink / GTalk) and the purchase never completes.
Apr 11, 2011
#4 sebapere...@gmail.com
I can also confirm having the same problem. Trying to buy the reserved product ids on the Dungeons Sample application, I get no IN_APP_NOTIFY, as described by poster above. 

I'm seeing this behavior on Android 2.1-update1.

These are the entries I get on the LogCat window:

WARN/GTalkService(151): [DataMsgMgr] broadcast intent callback: result=CANCELLED forIntent { act=android.intent.action.REMOTE_INTENT cat=[com.android.vending.billing.IN_APP_NOTIFY] (has extras) }
WARN/GTalkService(151): TODO: implement reportNoReceiverError!

I am wondering what does the GTalkService have to do with the IN_APP_NOTIFY notification.

Apr 11, 2011
#5 sebapere...@gmail.com
Some more info to validate that this is an Android Market issue.

I got a new phone, HTC Atria, with android 2.1u1, tried the sample it didn't work as expected, same issue as described above.
I updated the same phone to android 2.2.2, used the exact same apk, and the sample worked fine.
Apr 18, 2011
#6 kmans...@gmail.com
An update: now testing with a published application.

On 2.1, the Google Checkout window was taking a long time to close, so I pretended to be an impatient user and closed after about 15 seconds. The purchase confirmation was received another 15 seconds later or so.

On 2.2, the Google Checkout window closes almost immediately, and confirmation is received 1-2 seconds later. It's a much smoother experience for the user.

Apr 18, 2011
#7 ishihata...@gmail.com
I did an experiment.
I published my app and tried to buy a real item (not a android.test.* item) with 2.1 device. Then, the issue happened still.
On the other hand I could buy it without trouble by using 2.2 device. 
Apr 28, 2011
#8 NicolasG...@gmail.com
I'm not 100% sure if my issue 19 is exactly the same as this one.

I tested with a HTC Tattoo, HTC Dream and a Nexus One and on all of them the "Authorizing purchase" dialog stays for at least a minute with the last sign of life shown through a "RequestPurchaseBillingRequest: RESULT_OK" when the dialog disappears. Only restoring the transactions helps, which is completed in less than two seconds.

May 11, 2011
#9 davedr...@gmail.com
We are running into issues with 1.6 and 2.1 as well and its 'only' a medium priority and not a TOP priority?  Has Google directly addressed or responded??
May 16, 2011
#10 codemonk...@gmail.com
I'm having the same issue on my LG540 GT with 2.1u1 and HD Desire Z 2.2 ... this is bad... How can google expect us to use this when it doesnt event seem to work right?

It's not like in app payment is a minor feature...
May 17, 2011
#11 jonas.ma...@gmail.com
Same issue here.. HTC Hero 2.1u1

DEBUG/vending(5614): [1] BaseBuyPageActivity.onOrderResponse(): state: CART_PURCHASE response: [PurchaseResult=OK]

DEBUG/(5614): unable to unlink '/data/data/com.android.vending/cache/AVMC_PSU0FfaW5hcHA6bWUudmVydGV4LmhvdHZpYmVzOmFuZHJvaWQudGVzdC5wdXJjaGFzZWQ': No such file or directory (errno=2)

DEBUG/(5614): unable to unlink '/data/data/com.android.vending/cache/AVMC_SU0FfaW5hcHA6bWUudmVydGV4LmhvdHZpYmVzOmFuZHJvaWQudGVzdC5wdXJjaGFzZWQ': No such file or directory (errno=2)

0WARN/GTalkService(148): [DataMsgMgr] broadcast intent callback: result=CANCELLED forIntent { act=android.intent.action.REMOTE_INTENT cat=[com.android.vending.billing.IN_APP_NOTIFY] (has extras) }

WARN/GTalkService(148): TODO: implement reportNoReceiverError!

May 27, 2011
#12 codemonk...@gmail.com
I've flashed my phone to 2.3.3 with a Cynogenmod ROM ... This seems to solve the problem... but a rather drastic measure nontheless
May 27, 2011
#13 jonas.ma...@gmail.com
I tried that too, and on 2.3.3 it works perfectly well.
May 30, 2011
#14 martinwa...@gmail.com
Is there a fix for this? I'm using HTC Wildfire (2.1-update1) and I have the exact same issue.
Jun 8, 2011
Project Member #15 trevorjohns@google.com
(No comment was entered for this change.)
Status: Accepted
Labels: Google-4562998
Jul 6, 2011
#17 hiren.ka...@gmail.com
Did anyone get solution for this issue?
I am facing similar problems..
Jul 6, 2011
#18 jonas.ma...@gmail.com
Not yet, from what I know. Only use Google in-app billing if (Build.VERSION.SDK_INT > 7)
Aug 1, 2011
#20 mport...@gmail.com
Whoever accepted this bug, can we get an update?
Aug 9, 2011
#21 bher...@gmail.com
Anyone got an update for this?
Aug 25, 2011
#22 Andrey.Chorniy
I can't believe that this issue exists since April 10, 2011 and it still was not fixed and there is no any visible attempts to fix it. We spend a time to implement in-app-billing and now it turns out that it is not actually working. Really strange, since I'm sure that this feature is a driver for Android-Platform apps development and it's ignored by Market developers.

Why In-App-Billing documentation doesn't notify readers about this issue and the fact that it's actually not working service ? "http://developer.android.com/guide/market/billing/index.html"
Aug 25, 2011
#23 codemonk...@gmail.com
I agree with you Andrey. This issue still persists on test devices. 

Still the only (drastic) fix for this issue is to load a custom rom with Android 2.3 on your phone. Which is too absurd as it is...
Oct 11, 2011
#25 nani.al...@gmail.com
hi 
i am facing the same issue.my app not working for 2.1 and 1.6
i checked with above solution also.but its not working
Oct 11, 2011
#27 nani.al...@gmail.com
hi 
i am facing the same issue.my app not working for 2.1 and 1.6
i checked with above solution also.but its not working
Oct 24, 2011
#28 michael_...@booom.com.ph
hello
i am facing same issue, dungeons sample doesn't work for
sony-ericsson xperia running 2.1 .
i have a modified dungeons sample and the thing crashes during restore transactions,
anyone has done the same?

Nov 16, 2011
#29 ashish.w...@gmail.com
I am unable to run In app Billing Application on my android device Samsung ACE 2.2.1 version. I have market version 3.3.11 install on my device. I have follow all the steps of uploading APK on market but unable to run that app.
Jan 17, 2012
#30 cr...@franklinheath.co.uk
I tried the fix linked to in comment 24 on an HTC Tattoo (1.6), Market version 1002306.  The fix makes no difference, as the Market app is returning a valid response indicating that billing is supported, but it hangs after displaying the "Authorising purchase..." dialog.
Sign in to add a comment

Powered by Google Project Hosting