904137 - Sometimes, the Bango SMS takes forever

Status: RESOLVED FIXED

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

Description

[krupa raj[:krupa]]

Sometimes, during the MT auth step, the bango SMS takes forever to show up. We need a way to keep the user from getting frustrated waiting for the SMS to show up.

Comment 1

[Wil Clouser [:clouserw]]

Like a spinner or a retry button?  I don't think there is much we can do here.

Comment 2

[Kumar McMillan [:kumar]]

next time you see this, grab an http log or let me know so I can check the server logs and find the Billing Config ID so Bango can investigate.

Comment 3

[Andy McKay]

Is there anything else we should do here for the user? There is already a re-send button, should we show something if they stuck there for a certain amount of time.

Comment 4

[Maureen Hanratty]

Krupa and I talked about this. We thought instead of letting it take forever to wait 5 minutes and show an error message that the user has timed out. When the user attempts to purchase the app again we take them back to the "Confirm your mobile number" screen to re-enter their phone number.

Comment 5

[Kumar McMillan [:kumar]]

+1 for the 5 minute retry message. We should also gather some timing stats on this (if possible). Bango would need to instrument the timing measurement.

Comment 6

[Andy McKay]

Both the instrumentation of the timing and the returning to resend the SMS would be on Bangos end.

Comment 7

[Keir Kettle]

(In reply to Maureen Hanratty from comment #4)
> Krupa and I talked about this. We thought instead of letting it take forever
> to wait 5 minutes and show an error message that the user has timed out.
> When the user attempts to purchase the app again we take them back to the
> "Confirm your mobile number" screen to re-enter their phone number.


So if the user hasn't entered a valid PIN within 5 mins, 302 the request to the error URL defined in the BCID?

Comment 8

[Steve Ruston]

Maureen, Can you reply to Keir

Comment 9

[Maureen Hanratty]

(In reply to Keir Kettle from comment #7)
> (In reply to Maureen Hanratty from comment #4)
> > Krupa and I talked about this. We thought instead of letting it take forever
> > to wait 5 minutes and show an error message that the user has timed out.
> > When the user attempts to purchase the app again we take them back to the
> > "Confirm your mobile number" screen to re-enter their phone number.
> 
> 
> So if the user hasn't entered a valid PIN within 5 mins, 302 the request to
> the error URL defined in the BCID?

Yes, that sounds right.

Comment 10

[Tom]

Development is complete and will be uploaded to Production tomorrow.

Comment 11

[Kumar McMillan [:kumar]]

Thanks. Can someone provide details on what the resolution was? Are SMS messages always immediate now? If so, how immediate is immediate?

Comment 12

[Kumar McMillan [:kumar]]

Oh, is the resolution just to show the timeout message?

Comment 13

[Tom]

Kumar, we cannot control how quickly an aggregator or Operator SMS API sends an SMS so the best route to fix this was to 302 back to the error url after 5mins of waiting which means the user will timeout. That will result in the user having to re-authenticate.

Comment 14

[Steve Ruston]

Kumar, i am under the impression from the discussion with Krupa that this is normally whilst roaming, is that the case? If so then it takes a while for the sms to get through the home network and onto the roaming network potentially