Wrong Chrome profile used for authorization when relaunching for a Desktop app update

Pete De Bonte

Unusually, I had both my personal and work Chrome profiles open when I had the desktop app restart for an update.

1. As the desktop app relaunched, it showed an option to sign in or work offline.
2. I thought that was strange, but accepted the sign-in option (*shrug*)
3. A page (auth.Faithlife.com?) opened in my my work profile.
4. Not wanting to use my work account for this, I both:
   1. closed the work Chrome window
   2. clicked the ☒ in the desktop app's sign-in dialog
5. Started the desktop app (v46.1.5), and it started:
   1. without showing the sign-in option
   2. with the user icon/button in the toolbar showing my account

Non-repro (confusing!): I then retried launching the app with both Chrome profile windows open, but the app did not display the sign-in dialog (so I couldn't retest it). Might this occur only after an app update?

The version is now 46.1.5 (after restarting twice: once for the update and once for the retest shortly thereafter — I'm presuming the version didn't change between those).