Direct carrier billing doesn't function

[GoogleCodeExporter]

NTT DoCoMo and KDDI's direct carrier billing doesn't function for the In-app 
Billing system.

STEPS TO REPRODUCE:
1. Start In-app billing.
2. Choose the direct carrier billing as a payment method.
3. Push the 'Buy now' button.
4. Input the security password.

EXPECTED OUTPUT:
The billing is executed.

ACTUAL OUTPUT:
Nothing is executed.
It immediately returns to the screen of the app. The purchase request is 
completely disregarded.

AFFECTED ORDER IDS (IF RELEVANT):

OS VERSION:
2.2.1

MARKET/MYAPPS VERSION:
2.3.6

DEVICE:
IS05, Galaxy S

OUTPUT FROM ADB BUGREPORT ATTACHED:
Attached.

NOTES:
Followings are the Logcat messages immediately after the 'Buy now' button was 
pushed.

INFO/ActivityManager(295): Starting activity: Intent { 
cmp=com.android.vending/.billing.CarrierPasswordActivity (has extras) }
WARN/InputManagerService(295): Starting input on non-focused client 
com.android.internal.view.IInputMethodClient$Stub$Proxy@460f2c70 (uid=10089 
pid=1250)
INFO/BillingService(1250): handleCommand() action: 
com.android.vending.billing.RESPONSE_CODE
DEBUG/BillingService(1250): RequestPurchase: RESULT_USER_CANCELED
DEBUG/Dungeons(1250): potion_001: RESULT_USER_CANCELED
INFO/Dungeons(1250): user canceled purchase
INFO/ActivityManager(295): Displayed activity 
com.android.vending/.billing.CarrierPasswordActivity: 368 ms (total 368 ms)

It seems that the purchase request has been canceled at the same time as the 
CarrierPasswordActivity's being displayed.

Original issue reported on code.google.com by ishihata...@gmail.com on 12 May 2011 at 6:35

Attachments:

• bugreport.txt

[GoogleCodeExporter]

My users are reporting this too. Apparently carrier billing shows one more 
dialog after (on top?) of the Google Market 'Buy now' dialog. As soon as this 
dialog is displayed, the purchase is automatically cancelled.

Original comment by nikolay....@gmail.com on 24 May 2011 at 2:34

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Sounds like a serious issue if this still happens.  Will follow up.  - Ryosuke

Original comment by ryosu...@google.com on 4 Jul 2011 at 2:08

[GoogleCodeExporter]

We're working on this issue right now.  - Ryosuke

Original comment by ryosu...@google.com on 12 Jul 2011 at 9:04