The "Stay Alert to Data Breaches" card is not dismissed after logging in to "Firefox Monitor" with a newly created "Firefox Account"
Categories
(Firefox :: Messaging System, defect, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr68 | --- | unaffected |
firefox73 | --- | wontfix |
firefox74 | --- | wontfix |
firefox75 | --- | wontfix |
People
(Reporter: mcoman, Assigned: pdahiya)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
946.04 KB,
image/gif
|
Details |
[Notes]:
- This is not a tab preloading issue, because the "Stay Alert to Data Breaches" card is displayed on all five tabs after logging in to FxA.
[Affected versions]:
- Firefox Release 73.0 - Build ID: 20200207195153
- Firefox Beta 74.0b3 - Build ID: 20200214015126
- Firefox Nightly 75.0a1 - Build ID: 20200214100511
[Affected Platforms]:
- Windows 10 x64
- Mac 10.15.2
- Ubuntu 18.04 x64
[Prerequisites]:
- Have a Firefox profile with the "trailhead.firstrun.branches" pref set to "join-dynamic" in the "about:config" page.
- You are logged in to FxA using a NEW Firefox Account.
[Steps to reproduce]:
- Open the browser with the profile from prerequisites.
- Click the "Firefox Account" toolbar button and select the "Firefox Monitor" option.
- Click the "Sign In" button from the top-right part of the page.
- Click the "Sign In" button and open a new tab.
- Observe the displayed cards.
[Expected result]:
- The "Browse Privately", "Instantly Send Yourself Tabs" and "Get Firefox on Your Phone" cards are displayed.
[Actual result]:
- The "Stay Alert to Data Breaches" card is still displayed.
[Regression Window]:
- Considering the fact that this behavior is not reproducible on Firefox 72, using the mozregression tool I have managed to find the following regresion window:
Last good revision: 7dc3e0b9b5985852601ba0ece3c3a2764b9d1bc0
First bad revision: 440d0842a0aa25871aeb0b1b98c4292e7bb22e8d
Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=7dc3e0b9b5985852601ba0ece3c3a2764b9d1bc0&tochange=440d0842a0aa25871aeb0b1b98c4292e7bb22e8d
From the pushlog, it seems that bug 1600779 has caused this behavior.
[Additional Notes]:
- This issue is still reproducible after a page refresh.
- This issue is no longer reproducible after browser restart.
- This issue is not reproducible with older "Firefox Accounts".
- Attached a screen recording of the issue.
@Punam, could you please take a look over this issue?
Assignee | ||
Comment 1•5 years ago
|
||
@mcoman I believe this issue is duplicate of https://bugzilla.mozilla.org/show_bug.cgi?id=1603803 as its not replicable for old FxA account or on restart. I will look into it, can you please log steps of pre-requisite 'create a new FxA Account' that leads to this issue. Thanks
Updated•5 years ago
|
Reporter | ||
Comment 2•5 years ago
|
||
Hi Punam, in order to create a new FxA account we used the following steps:
[Prerequisites]:
- Have a valid email address that was never linked to a FxA account before.
[Steps]:
- Open the browser and navigate to the "about:welcome" page.
- Enter the email from prerequisites in the text field and click the "Continue" button.
- Complete the sign-up form and click the "Create account" button.
- Enter the 6-digit code received on the email from prerequisites and click the "Verify" button.
I hope it helps. If you will need other information you can ping me anytime here or on slack (mcoman).
Updated•5 years ago
|
Assignee | ||
Comment 3•5 years ago
|
||
Thanks @mconman, the underlying issue is similar to https://bugzilla.mozilla.org/show_bug.cgi?id=1600779#c14 . fxAccounts.listAttachedOAuthClients() API call returns error "UNVERIFIED_ACCOUNT" for new accounts, with caching in place the next call to retrive attached client happens after 2 hrs or on browser restart. Marking issue as duplicate of 1603803
Assignee | ||
Updated•5 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Description
•