1152305 - Error when trying to reset PIN from payment screen on marketplace-dev on FxOS

Status: RESOLVED DUPLICATE of bug 1150884

(Marketplace Graveyard :: Payments/Refunds, defect)

Description

[Bob Silverberg [:bsilverberg]]

Attachment: Error message when trying to reset PIN

STR:

1. Launch marketplace-dev on a FxOS device
2. Login
3. Set the region to 'United States'
4. Choose to install the app 'Test Zippy With Me', which should launch the payment flow
5. Create / confirm a PIN
6. Cancel payment
7. Choose to install the app again, which should launch the payment flow again
8. Tap 'Forgot your PIN?'
9. Tap the 'Reset' button

At this point we expect the FxA login screen to appear, but instead an error is displayed 'An error ocurred whilst trying to log out.
See attached screenshot.

Note that this is 100% reproducible in our automated test, but is more difficult to reproduce manually as step 9 needs to occur very quickly after step 8 to reproduce. If you pause before tapping the 'Reset' button is does not reproduce.

Because of the above, this may not be considered a very important bug. It is unlikely that a user will encounter it. But it might be interesting to the dev team to look into to see why it is happening. It could be a symptom of something else that should be addressed.

Comment 1

[Stuart Colville [:muffinresearch]]

This sounds very similar to bug 1150884. But, the fix for that landed on -dev yesterday.

I will see if I can manually repro.

Comment 2

[Stuart Colville [:muffinresearch]]

@bsilverberg has this only just started happening for automation or has it been something that's been happening for a while?

Comment 3

[Bob Silverberg [:bsilverberg]]

It's been happening since April 2, although it's possible it's now fixed, as I was looking at yesterday's report at the failure. I'm pretty sure I reproduced it again today locally, but it seems to be passing for me now locally. I'll try a few more runs to see what happens.

Comment 4

[Bob Silverberg [:bsilverberg]]

This does seem to be fixed now for me. I thought I had a local failure today, but could be mistaken. I will mark this as a duplicate of bug 1150884 as it does seem to be fixed. Sorry for the noise.