search

Eymir / marketbilling

Automatically exported from code.google.com/p/marketbilling
0 stars 0 forks source link

In-App Billing does not work on Android 1.6 and 2.1 #7

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
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.

Original issue reported on code.google.com by ishihata...@gmail.com on 11 Apr 2011 at 6:40

GoogleCodeExporter commented 9 years ago 
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.

Original comment by kmans...@gmail.com on 11 Apr 2011 at 7:48

GoogleCodeExporter commented 9 years ago 
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.

Original comment by nathan.s...@gmail.com on 11 Apr 2011 at 10:35

GoogleCodeExporter commented 9 years ago 
>>>
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.

Original comment by kmans...@gmail.com on 11 Apr 2011 at 1:54

GoogleCodeExporter commented 9 years ago 
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.

Original comment by sebapere...@gmail.com on 11 Apr 2011 at 4:53

GoogleCodeExporter commented 9 years ago 
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.

Original comment by sebapere...@gmail.com on 12 Apr 2011 at 5:45

GoogleCodeExporter commented 9 years ago 
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.

Original comment by kmans...@gmail.com on 18 Apr 2011 at 8:47

GoogleCodeExporter commented 9 years ago 
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.

Original comment by ishihata...@gmail.com on 18 Apr 2011 at 9:32

GoogleCodeExporter commented 9 years ago 
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.

Original comment by NicolasG...@gmail.com on 28 Apr 2011 at 4:56

GoogleCodeExporter commented 9 years ago 
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??

Original comment by davedr...@gmail.com on 11 May 2011 at 2:43

GoogleCodeExporter commented 9 years ago 
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...

Original comment by codemonk...@gmail.com on 16 May 2011 at 11:08

GoogleCodeExporter commented 9 years ago 
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_PSU0FfaW5hcHA6bWUudmVydGV4LmhvdHZpYmV
zOmFuZHJvaWQudGVzdC5wdXJjaGFzZWQ': No such file or directory (errno=2)

DEBUG/(5614): unable to unlink 
'/data/data/com.android.vending/cache/AVMC_SU0FfaW5hcHA6bWUudmVydGV4LmhvdHZpYmVz
OmFuZHJvaWQudGVzdC5wdXJjaGFzZWQ': 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!

Original comment by jonas.ma...@gmail.com on 17 May 2011 at 11:11

GoogleCodeExporter commented 9 years ago 
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

Original comment by codemonk...@gmail.com on 27 May 2011 at 9:18

GoogleCodeExporter commented 9 years ago 
I tried that too, and on 2.3.3 it works perfectly well.

Original comment by jonas.ma...@gmail.com on 27 May 2011 at 9:27

GoogleCodeExporter commented 9 years ago 
Is there a fix for this? I'm using HTC Wildfire (2.1-update1) and I have the 
exact same issue.

Original comment by martinwa...@gmail.com on 30 May 2011 at 7:56

GoogleCodeExporter commented 9 years ago

Original comment by trevorjohns@google.com on 8 Jun 2011 at 5:07

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Did anyone get solution for this issue?
I am facing similar problems..

Original comment by hiren.ka...@gmail.com on 7 Jul 2011 at 5:23

GoogleCodeExporter commented 9 years ago 
Not yet, from what I know. Only use Google in-app billing if 
(Build.VERSION.SDK_INT > 7)

Original comment by jonas.ma...@gmail.com on 7 Jul 2011 at 5:52

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Whoever accepted this bug, can we get an update?

Original comment by mport...@gmail.com on 2 Aug 2011 at 2:19

GoogleCodeExporter commented 9 years ago 
Anyone got an update for this?

Original comment by bher...@gmail.com on 9 Aug 2011 at 1:14

GoogleCodeExporter commented 9 years ago 
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"

Original comment by Andrey.Chorniy on 25 Aug 2011 at 8:17

GoogleCodeExporter commented 9 years ago 
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...

Original comment by codemonk...@gmail.com on 25 Aug 2011 at 8:27

GoogleCodeExporter commented 9 years ago 
Anybody seen/tried this answer yet?

http://stackoverflow.com/questions/5576733/in-app-billing-is-not-working-on-g1

Original comment by mport...@gmail.com on 28 Aug 2011 at 10:02

GoogleCodeExporter commented 9 years ago 
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

Original comment by nani.al...@gmail.com on 12 Oct 2011 at 4:41

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
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

Original comment by nani.al...@gmail.com on 12 Oct 2011 at 5:12

GoogleCodeExporter commented 9 years ago 
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?

Original comment by michael_...@booom.com.ph on 24 Oct 2011 at 8:23

GoogleCodeExporter commented 9 years ago 
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.

Original comment by ashish.w...@gmail.com on 17 Nov 2011 at 5:42

GoogleCodeExporter commented 9 years ago 
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.

Original comment by cr...@franklinheath.co.uk on 17 Jan 2012 at 11:22

GoogleCodeExporter commented 9 years ago 
I found weired issue yestreday my alpha testers are chraged while in-app 
purchages and I have to refund money to them. is it a bug in Google Play. I 
could release my prodct earlier tested by alpha testers without any hitch.

Original comment by sandeeps...@gmail.com on 27 Jan 2015 at 8:47