Closed
Bug 1082204
Opened 10 years ago
Closed 10 years ago
[dev] Blank screen loads instead of the FxA screen during app purchase
Categories
(Marketplace Graveyard :: Payments/Refunds, defect, P1)
Tracking
(Not tracked)
VERIFIED
FIXED
2014-10-21
People
(Reporter: krupa.mozbugs, Assigned: ckarlof)
References
Details
Attachments
(1 file)
(deleted),
video/quicktime
|
Details |
Connectivity: wifi
SIM used: none
Gaia/device: flame(kk)/2.0 [2014-09-04 7:42:57 506da297]
NOTE: not the same as https://bugzilla.mozilla.org/show_bug.cgi?id=1079382. The blank screen is happening before the FxA screen.
steps to reproduce:
1. Search for :paid app on your payments-alt app
2. Start the purchase of a paid app
3. Click on the Sign in button
observed behavior:
FxA screen loads
actual behavior:
blank screen loads after clicking Sign in
Updated•10 years ago
|
Priority: -- → P1
Assignee: nobody → amckay
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → 2014-10-21
We're not seeing this on payments-alt any more but we are seeing this on -dev (marketplace-dev.allizom.org)
On device we see a blank screen. We can see the url for FxA being requested.
Trying this on a desktop browser I see https://www.evernote.com/shard/s8/sh/8acba7da-3303-4a62-bea6-a535faa838ca/a5fb66c460f8b7947a7a126f1ba315fc/deep/0/Firefox-Accounts.png which would explain the white screen seen on device.
STR:
* Open https://marketplace-dev.allizom.org/mozpay/
* Click on Sign-in
What happens:
* Blank UI
Note: In the console there's a 400 BAD request to:
https://oauth-stable.dev.lcip.org/v1/client/<client-id>
Where <client-id> matches the client_id param in the original request to https://oauth-stable.dev.lcip.org/v1/authorization
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 3•10 years ago
|
||
Configuration in the stable server needed to be updated. This is resolved.
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Flags: needinfo?(ckarlof)
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•