Closed Bug 974894 Opened 12 years ago Closed 12 years ago

Users are not asked for phone number confirmation PIN sent via SMS for a first purchase with a new account

Categories

(Marketplace Graveyard :: Payments/Refunds, defect)

Avenir
x86_64
Windows 7
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX
2014-02-25

People

(Reporter: vcarciu, Unassigned)

Details

(Keywords: regression)

Prerequisites: Inari device, build 1.2 , MP-stage installed WI-fi enabled, region set to Spain, Movistar SIM Steps to reproduce: 1.Open MP-stage app and use a new address for sign-up 2.Find a paid app and start the purchase process 3.Create a new PIN and continue 4.Enter the required phone number and continue Expected results: User is asked to confirm the phone number by entering a code received via SMS Actual results: User is directly provided with confirm purchase page, no SMS is received and user is not asked for this step Logs ID: 6fc9e
this is by design now. We landed silent SMS on stage but it wasn't working me. I'll check again.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
Krupa, in this case I think that I have an useful update : the silent SMS feature is working only with Movistar SIM and region set to Spain. Iulian checked with the US SIM and and the number confirmation PIN was sent via SMS for him.
Resolution: WONTFIX → FIXED
Resolution: FIXED → WONTFIX
(In reply to Victor Carciu from comment #2) > Krupa, in this case I think that I have an useful update : the silent SMS > feature is working only with Movistar SIM and region set to Spain. > > Iulian checked with the US SIM and and the number confirmation PIN was sent > via SMS for him. interesting. I will try to reproduce and have a bug for it.
Please make also sure that the system that is having problems in the US is a version that supports Silent SMS. I think >= 1.1 and the purchase is being made in the Trusted UI. A system that does not support window.mozPaymentProvider.observeSilentSms is the only reason I can think of at the moment that would show a behavior where the silentSMS is just flat out ignored. Any possible error would result most likely in having to wait for the silenSMS timeout.
You need to log in before you can comment on or make changes to this bug.