860259 - [b2g] "Payment failed. Try again later" message is displayed every time when trying to buy an app

Status: RESOLVED WORKSFORME

(Marketplace Graveyard :: Payments/Refunds, defect)

Description

[Victor Carciu]

Attachment: Logcat

Prerequisites:
Unagi device with latest build installed from https://releases.mozilla.com/b2g/(1.1.0.0)
MP-dev app installed from http://people.mozilla.org/~kmcmillan/mktdev.html
Movistar SIM , roaming activated

Steps to reproduce:
1.Login to MP-dev app with valid credentials
2.Find a paid app(ie. "Test App(baboon71)") and press the price button

Expected results:
The "Enter PIN" screen is displayed and users are able to buy the apps following purchase flow

Actual results:
"Payment failed. Try again later" message is displayed for every paid app 

Please see attached logcat

Comment 1

[Kumar McMillan [:kumar]]

in logcat: "navigator.mozPay error: PAY_REQUEST_ERROR_NO_VALID_REQUEST_FOUND"

This error means your device's payment preferences are configured to use the Marketplace Dev server. Could you make sure you have pushed these prefs? https://github.com/mozilla/webpay/blob/master/ezboot/custom-prefs.js

Here's an automated way to configure an Unagi device with test preferences: https://webpay.readthedocs.org/en/latest/use_hosted_webpay.html#set-up-a-device-with-ezboot

Comment 2

[Victor Carciu]

(In reply to Kumar McMillan [:kumar] from comment #1)
> in logcat: "navigator.mozPay error: PAY_REQUEST_ERROR_NO_VALID_REQUEST_FOUND"
> 
> This error means your device's payment preferences are configured to use the
> Marketplace Dev server. Could you make sure you have pushed these prefs?
> https://github.com/mozilla/webpay/blob/master/ezboot/custom-prefs.js
> 
> Here's an automated way to configure an Unagi device with test preferences:
> https://webpay.readthedocs.org/en/latest/use_hosted_webpay.html#set-up-a-
> device-with-ezboot

We pushed the correct preferences and now the PIN is required and user is asked for the phone number when a correct PIN is entered.
Unfortunately nothing happened after entering the correct mobile phone number(we tried many variants without success). Please note that we are using a Telefonica SIM and Spain is detected automatically so the location should not be a problem.
We will attach again the logcat and also the actual user.js file .
Please help us to find a solution for this problem.

Comment 3

[Victor Carciu]

Attachment: Logcat after entering the mobile number

Comment 4

[Victor Carciu]

Attachment: Modified user.js file

Comment 5

[Kumar McMillan [:kumar]]

Hi Victor. You are correct, the confirm-your-number screen should not show up when on a Telefonica SIM.

Can you attach an HTTP log? This is separate from logcat. HTTP logging will help us see what the responses are from the MobileID service. I do HTTP logging with `ezboot http` https://github.com/kumar303/ezboot More info here: https://developer.mozilla.org/en-US/docs/Mozilla/Debugging/HTTP_logging#Firefox_OS_phones

Also, make sure that 'console logging' is enabled in your Developer settings on device. The logcat you pasted does not have any log messages.

Comment 6

[Kumar McMillan [:kumar]]

You also must have wifi disabled and cell network data enabled

Comment 7

[Victor Carciu]

Wifi is disabled and we are working with data and roaming enabled.

Comment 8

[Cristian Boldan]

Attachment: logcat payment failed

I have tried to make a purchase, with the user.js file modified. It worked yesterday (worked to the mobile number step), but now it says Payment failed, and unfortunately I cannot make a HTTP logging because of this. I have attached the logcat with this issue. I have tried all the possibilities but nothing worked.

Comment 9

[Kumar McMillan [:kumar]]

You still don't have payments prefs set up. You can find info on how to set it up from this guide: https://webpay.readthedocs.org/en/latest/use_hosted_webpay.html#build-a-custom-b2g-profile

Comment 10

[Kumar McMillan [:kumar]]

To clarify: the logcat suggests that you don't have the right prefs. Can you pastebin your prefs if you are sure that they are in user.js and on the device?