Closed Bug 1061923 Opened 10 years ago Closed 10 years ago

Purchase flow is stuck at "Initializing.." screen

Categories

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

x86
Gonk (Firefox OS)
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: krupa.mozbugs, Assigned: scolville)

References

Details

Attachments

(2 files)

Attached file logcat-initializing.txt (deleted) —
Connectivity: wifi, Data raoming enabled
SIM used: Movistar Spain
Gaia/device: 1.4/hamachi


steps to reproduce:
0. Tester is not logged in
1. Load feedStage app on your firefoxOS phone
2. Search for :paid 
3. Start the purchase flow of an app
4. Sign in using persona

expected behavior:
After signing in, the Create/Enter PIN screen loads

actual behavior:
After signing in, the purchase flow is stuck at the initializing screen
Attached image screenshot (deleted) —
How do I install Feedstage - I found it on -dev but can't install it - it says "Download stopped".
Priority: -- → P2
Krupa: I've got feedstage installed - but I can't reproduce with hamachi running 1.3.

Does this repro for all versions or just the dreaded hamachi/1.4 ?

The code you're reaching doesn't look like it should happen - I'll add some extra logging in so we can see what is making that a dead-end in-case that sheds any light on the issue.

Logging added here:

https://github.com/mozilla/spartacus/commit/94cef1666dab3ee3f90dbe6c68a7ba493ea897b4
I can see where this dead-end is coming from. Persona fires onready when loggedInUser is not set. This results in nothing happening. This PR adds a fix to ensure that if onready is called on its own and loggedInUser is unset we show the login view:

https://github.com/mozilla/spartacus/pull/124
Assignee: nobody → scolville
Status: NEW → ASSIGNED
This will thus mean that the user will need to jump through a login step, but at least you aren't left hanging with no place to go.
https://github.com/mozilla/spartacus/commit/afbce6db5cdfa41e2090dba3194be610b9ad3cb6

QA Notes:

 This should mean the original STR are no longer reproduceable - instead you will see a similar experience to bug 1057033 - which isn't yet fixed.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: