Web page or screen you were on when you saw the issue: visit www.kobo.com Steps to reproduce: 1. Try to login 2. Login page loads 3. FFbeta2 crashes (has happened twice) What you expected: Crash report ID (if applicable): bp-f6901349-3bc7-48f7-bcc2-fd13b2120521 bp-87119601-49d9-4516-9ad6-e26592120521

Only one version of Firefox for mobile is allowed when using Sync. Do you use also the release version?

When I downloaded Beta2, I deactivated sync for Aurora which I'd been using previously. My sync account is otherwise connected to Firefox Home.

(In reply to Chelsea Novak [:chelsea] from comment #3) > When I downloaded Beta2, I deactivated sync for Aurora which I'd been using > previously. My sync account is otherwise connected to Firefox Home. When you say "deactivated", do you mean: * You chose "Remove Account" in the account settings app? * You unchecked the box labeled "Firefox Aurora"? * Something else? This crash log implies that you have two versions of Firefox installed (presumably Aurora and Beta), and the one that's trying to sync is not the one that Android thinks "owns" the account. This is why we phrased the constraint as "you can only have one version of Firefox installed", rather than "you can only have Sync turned on for one version of Firefox". We can't predict accurately whether the latter will work, and in your case it does not. It's coincidence that this crash is occurring while you're browsing.

> When you say "deactivated", do you mean: > > * You chose "Remove Account" in the account settings app? > * You unchecked the box labeled "Firefox Aurora"? > * Something else? > I did the first two actions you listed there. > This is why we phrased the constraint as "you can only have one version of > Firefox installed", rather than "you can only have Sync turned on for one > version of Firefox". We can't predict accurately whether the latter will > work, and in your case it does not. It makes sense that you can't predict that. As a user, I did not infer that from the way it was phrased and found the experience very confusing (and still do in truth), I wouldn't know what to do next after I encounter that error. I'm sure the crashing didn't help either. > It's coincidence that this crash is occurring while you're browsing. Okay.

(In reply to Chelsea Novak [:chelsea] from comment #5) > It makes sense that you can't predict that. As a user, I did not infer that > from the way it was phrased and found the experience very confusing (and > still do in truth), I wouldn't know what to do next after I encounter that > error. I'm sure the crashing didn't help either. Yeah, our UX here sucks really bad :/

P5: won't be directly addressed; see Bug 761206, which will take care of this.

How do we feel about FIXED WORKSFORME? Work on Bug 761206 (specifically, Bug 772645) has essentially addressed this.