879171 - If the user selects in-app and change any price point , error message will be displayed (Durango)

Status: RESOLVED FIXED

(Marketplace Graveyard :: Payments/Refunds, defect, P1)

Description

[Vikas Nanda]

Attachment: ezboot-http.log

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:21.0) Gecko/20100101 Firefox/21.0 (Beta/Release)
Build ID: 20130511120803

Steps to reproduce:

After the user has changed the pricetier the user will be redirected to the in app payment where an error message will be shown which reads "Sorry there was a problem. Please try again later". 

steps to reproduce:

1- install In-App Payment tester app installed
2- Open In-App application and change the pricetier value
3- Call the browser (call navigator.mozPay())
4- Enter the Pin
5- Enter the mobile number
6- Notice the error message "Sorry, there was a problem. Please try again later.





Actual results:

The payment fails the user is presented with the error message, "Sorry, there was a problem. Please try again later."



Expected results:

The Payment should successfully go through.

Comment 1

[Vikas Nanda]

Attachment: screenshot of error message

Comment 2

[Vikas Nanda]

Notice this issue occurs only when pricepoint 1 is selected.

Comment 3

[Kumar McMillan [:kumar]]

This is a Bango error. The entry point is:

https://mozilla.bango.net/mozpayments/?bcid=15521860

If this is a price point problem then Bango should be redirecting to our error handler instead of displaying this message.

Comment 4

[Steve Ruston]

on test in Bango

Comment 5

[Vikas Nanda]

This issue is reproducible. New logs included.

Comment 6

[Vikas Nanda]

Attachment: ezboot log

Comment 7

[Keir Kettle]

The title is a bit misleading - the actual issue is the SMS sending fails.

There was another bug opened about this, but I can't find it.  The issue in a nutshell is we are using a tmon API to send SMS, currently we only have access provisioned from our  test to their test platform (Moz dev).

Comment 8

[krupa raj[:krupa]]

Talked to Vikas who is our Durango tester and this issue is not reproducible on stage.