Closed Bug 750746 Opened 12 years ago Closed 12 years ago

Wrong instructions in Fennec Sync setup screen

Categories

(Firefox for Android Graveyard :: Android Sync, defect, P1)

Product:
Firefox for Android Graveyard
Component:
Android Sync
Platform:
ARM
Android
Type:
defect

Tracking

(blocking-fennec1.0 -, fennec+)

Status:
VERIFIED FIXED
Milestone:
mozilla15
Tracking Flags:
Tracking Status
blocking-fennec1.0 --- -
fennec + ---

People

(Reporter: gcp, Assigned: liuche)

Details

(Whiteboard: sync) 

The instructions that Native Fennec gives for pairing a new device with Native Fennec are wrong. 

Scenario: Native Fennec syncs setup. New desktop installation.

Launch Fennec->Settings->Sync->Accounts->Firefox Sync->Pair A Device

The instructions say: "Select "Pair a Device" in the Sync section of your desktop Firefox options. This is incorrect: the user must select "Set up Sync" first, not "Pair a Device". 

If (s)he selects "Pair a Device" as instructed, he'll get the same screen as Native Fennec is showing for entering the JPAKE code, with both devices expecting it will be entered.

If (s)he selects "Set up Sync" (and perhaps needs to select "Pair a device" in a screen *thereafter* - I don't remember for sure) then the JPAKE code will be shown and can be entered in Native Fennec.
blocking-fennec1.0: --- → ?
Whiteboard: sync
Drat.

Fortunately this is a fairly rare scenario!

Can't block 1.0 -- would need string changes.
Component: General → Android Sync
Product: Fennec Native → Mozilla Services
QA Contact: general → android-sync
Version: Trunk → unspecified
The use case where you get this is if you're setting up a new PC (or have just installed Firefox on a machine you're going to use), and you want to access your bookmarks/history -> your Fennec phone which you have with you is the one where you can get the Sync key off.
sync triage: - for breaking string freeze
(In reply to Gian-Carlo Pascutto (:gcp) from comment #2)
> The use case where you get this is if you're setting up a new PC ...

Yup, that's fairly uncommon. If this were the flow for setting up a new phone from a desktop, I'd be really concerned.
Chenxia, when you have a chance, can you please check that we are not doing anything thing too foolish, such as using the wrong string? thanks
Assignee: nobody → liuche
tracking-fennec: --- → +
blocking-fennec1.0: ? → -
No chance of unfreezing string freeze? We're not using the wrong string, the string for pairing is just wrong.
tracking-fennec: + → ---
blocking-fennec1.0: - → ?
(In reply to Chenxia Liu [:liuche] from comment #6)
> No chance of unfreezing string freeze? We're not using the wrong string, the
> string for pairing is just wrong.

We're six days from beta, so I wouldn't say there's a chance. We just need to fix this for the next release.
(Someone with Bugzilla magic fingers please fix flags after they were Bugzilla'd in Comment 6.)
Priority: -- → P1
tracking-fennec: --- → +
blocking-fennec1.0: ? → -
Whiteboard: sync → sync, [need review: rnewman]
Whiteboard: sync, [need review: rnewman] → sync, [needs review: rnewman]
Building this before I land.
Status: NEW → ASSIGNED
Whiteboard: sync, [needs review: rnewman] → sync
I backed this out while sorting through a bunch of orange.  It'll need to be relanded.

https://hg.mozilla.org/integration/mozilla-inbound/rev/e032026e433c
https://hg.mozilla.org/mozilla-central/rev/460cc56982ec
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Flags: in-testsuite-
Resolution: --- → FIXED
verified in latest nightly
Status: RESOLVED → VERIFIED
Product: Mozilla Services → Android Background Services
Product: Android Background Services → Firefox for Android
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.