Closed
Bug 1145839
Opened 11 years ago
Closed 11 years ago
Unable to confirm new accounts on BuddyUp
Categories
(support.mozilla.org :: BuddyUp, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: marcia, Assigned: rik)
References
Details
(Keywords: regression, Whiteboard: p=1 s=bu.2015.5 [blocker])
Attachments
(1 file)
Using the latest pull from Github, I cannot confirm a new account.
STR:
1. Go into Profile
2. Create a new account
3. Confirm the email to activate the account.
Expected: I would be taken to the Support homepage or I would move off the "Confirm your Account" Screen
Actual: I cannot get out of the Confirm your Account Screen, even after closing and reopening the app. The only way to exit is to cancel the email confirmation.
I tested this on two different devices with two new accounts and received the same result. Using an existing account still works.
Comment 1•11 years ago
|
||
This bug is a regression introduced by this commit:
https://github.com/mozilla/buddyup/commit/29e5b87da7ae6acbb7f83787fc146e5d0e333abb
Keywords: regression
| Assignee | ||
Updated•11 years ago
|
Whiteboard: p=1 s=bu.2015.5 [blocker]
| Assignee | ||
Updated•11 years ago
|
Assignee: nobody → anthony
Status: NEW → ASSIGNED
| Assignee | ||
Comment 2•11 years ago
|
||
We had an error saying that Utils was undefined. That's because SumoDB now requires utils.js and it wasn't included on that page.
I took the opportunity to verify if other files had this problem and it doesn't seem so.
I used this command to list them:
ag -l sumo_db.js|grep html|xargs grep -L '/utils.js'
| Assignee | ||
Comment 3•11 years ago
|
||
Attachment #8581586 -
Flags: review?(rdalal)
Updated•11 years ago
|
Attachment #8581586 -
Flags: review?(rdalal) → review+
| Assignee | ||
Comment 4•11 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Flags: needinfo?(mozillamarcia.knous)
Flags: needinfo?(hcondei)
Resolution: --- → FIXED
Updated•11 years ago
|
Status: RESOLVED → VERIFIED
Flags: needinfo?(mozillamarcia.knous)
You need to log in
before you can comment on or make changes to this bug.
Description
•