Closed Bug 1179328 Opened 9 years ago Closed 6 years ago

Clicking verification link in email on another device does not clear "A verification link has been sent" screen

Categories

(Firefox OS Graveyard :: FxA, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(tracking-b2g:backlog, b2g-v2.2 affected, b2g-master affected)

RESOLVED WONTFIX
tracking-b2g backlog
Tracking Status
b2g-v2.2 --- affected
b2g-master --- affected

People

(Reporter: scabral, Unassigned)

Details

(Keywords: foxfood)

Attachments

(1 file)

Clicking verification link in email on another device does not clear "A verification link has been sent" screen
If I leave the phone open and unlocked at the Firefox account "A verification link has been sent" screen, it doesn't recognize when I eventually click the verification link. It'd be nice if it polls the server to see if it was actually clicked. Or sent a notification when it logged in. Or anything, really, other than just showing me 'yeah, we sent a link' which is factually true but ultimately of no relevance once I've clicked it.
Component: General → FxA
QA Whiteboard: [foxfood-triage]
Keywords: qawanted
Attached video Flame2.2.3gp
Hi Sherri,
 I try to repro this bug  on latest build of Fame2.2 & master. Here comes my STR and results. Could you please help to confirm whether it is corresponding with comment 0? Thanks very much!

STR:
 1.Launch Settings->Firefox Account
 2.Tap the Create Account or Sign in bar
 3.Fill the email adress ,year and password and get into next.
 4.Tap "Resend".
 **It will prompt  "A verification link has been sent". 
 5.Tap "verify" on another device.
Antual results: The prompt  "A verification link has been sent" will not be cleared if you don't tap OK"on DUT.

Note: Tap "OK" on "A verification link has been sent" view of DUT. It will jump the Firefox Accounts view and  signed in sucessfully.

See video: Flame2.2.3gp

Device information:
Flame 2.2:
Build ID               20150719002503
Gaia Revision          e1e6317f17a840b19af9dbb25f5a771d8d9fa161
Gaia Date              2015-07-15 21:05:11
Gecko Revision         https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/e2d1f1f55803
Gecko Version          37.0
Device Name            flame
Firmware(Release)      4.4.2
Firmware(Incremental)  eng.cltbld.20150719.041302
Firmware Date          Sun Jul 19 04:13:13 EDT 2015
Bootloader             L1TC000118D0

Flame master: 
Build ID               20150719010204
Gaia Revision          3fac3ed7b8c887351098ffc677769ddc36abb3d0
Gaia Date              2015-07-17 17:53:41
Gecko Revision         https://hg.mozilla.org/mozilla-central/rev/9c919ce631ea
Gecko Version          42.0a1
Device Name            flame
Firmware(Release)      4.4.2
Firmware(Incremental)  eng.cltbld.20150719.050227
Firmware Date          Sun Jul 19 05:02:38 EDT 2015
Bootloader             L1TC000118D0
Flags: needinfo?(scabral)
Flags: needinfo?(scabral) → needinfo?(rsoderberg)
According to comment 2, this bug can be repro on Flame 2.2 & master.
Yes, those steps to reproduce are accurate.
Flags: needinfo?(rsoderberg)
[Tracking Requested - why for this release]:

Moving to backlog since FxA bugs in B2G are not actively being resolved at the moment.
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: