Regretably, I would say it does not pass UAT as of right now. I couldn't get Firefox Accounts to sign me in on my FxOS 1.1 device. Currently none of the user stories pass. I will reclaim my other Firefox OS device and/or try on the simulator with latter versions of FxOS. Possibly it is related to the version of FxOS I am running on with an Unagi device.

Krupa - Can you help dbialer get onto the right device so he can evaluate the flows?

Ryan - Please let us know if the migration flow has met the ux spec as built. where it has not, please comment in bug. We can work together to triage into P1, P2, etc Caitlin

As discussed in yesterday’s email thread, the current experience does match the provided UX. When the user attempts to log in, until the migration period has ended, the user should only see the email field which can be used to determine the appropriate experience (migration, login or other edge cases). The current experience does not accommodate users who have reset their phones (common for developers) or have replaced their phones. Are there accounts in the other states I can use to test registration with? Obviously I have no previously existing accounts on staging. Please send.

David, You should be able to sign in using FxA on 1.1 since the JS error was fixed on stage.

Spent the evening testing on desktop only. Speaking with Andy and Mark today I realize that there is work remaining to match the original flows. Still, I came across many issues during circuitous rounds of account creation, login, migration using combinations of Firefox profiles, Sync, other browsers and my iPhone. Rough notes outlining good, bad and mixed news: = good news = i tried to register with an existing fxa it said "account exists, sign in" i signed in it worked! = mixed news = persona01@ryanfeeley.com signed in using safari ran console message to turn account into persona account did migration created a new account persona01@ryanfeeley.com all popups open in new tabs, and i can't switch the tab back (focus is forced on "popup" tab) on my iphone email client, i clicked the verification link safari tab closed, and i was signed in but no toast appeared = bad news = persona02@ryanfeeley.com ran console message to turn account into persona account verification email slow to come transitioned with a different email in a different client tried to register first with existing account but then sign in was returned to marketplace but sign in failed, stated so in the toast = bad news = persona03@ryanfeeley.com signed in to new account ran console message to turn account into persona account refreshed and saw banner signed out (banner still visible) clicked sign in transition message screen came up (bad experience for shared device) should show email only form = bad news = not signed in, but was previously clicked registration only fxa registration should ever be shown currently shows transition message in popup = good news = from email only form, entered a unknown account was taken to auto-filled registration as planned = bad news = fxa09@ryanfeeley.com created an account verified on phone signed out of one marketplace user clicked sign in saw the transition message screen entered newly verified email was shown auto-filled registration screen, not login screen but when i did login, it worked in safari but not in firefox i reset the password and still the same thing i can sign in on safari but not in firefox is the account caching a token with the old password somehow?

Something else odd I noticed is that while the popup is up, and Marketplace is waiting for closure, the CPU usage goes through the roof.

It is fixed. I tested on FxOS 1.1 and Desktop the paths: signing up for a new firefox account trying to register a new Fx Account with an existing Persona email address. transition to a new FxAccount with an existing unverified Persona account transition to a new FxAccount with an existing verified email address. With the exception of several outstanding bugs and some user flows (Bug 1094498) it looks like it correctly transitions users to Fx Accounts. We can solve today in standup perhaps?

Hey there Ryan and David Bialer - Does the current build satisfy the product requirements and ux specs? Do you have any concerns / bugs we need to take on for after go-live, as part of a cleanup / stabilization activity?

This was pushed live.

Case closed.