CloudServices/Sync/Transition testing

Overview

Sync 1.1 will eventually go away. We need to message users and transition them in a seamless way. If you're interested in testing that flow, follow the instructions below.

Instructions

WARNING!!! Please use a test Profile, do not use your primary profile as data loss may occur

Instructions on creating new and backing up profiles: https://support.mozilla.org/en-US/kb/back-and-restore-information-firefox-profiles

This describes how to test the Sync migration from 1.1 (jpake pairing) to 1.5 (Firefox Account).

Configuring Firefox for legacy Sync

Although not supported, there is a trick you can use to configure recent Firefox versions with legacy sync.

• Ensure any existing sync accounts are fully disconnected from the profile.

• Via about:config, create a new string preference services.sync.username and enter the value dummy

• Restart the browser

• Open Preferences and select the Sync pane - you should see the legacy sync setup.

From here you can either create a new legacy sync account or use an existing one (but only ones previously created against the test sync server - see below). Note however that if you reuse an existing account which has already been used for migration testing, the UX will be the same as if this is the second device to be migrated (ie, you should find about:accounts pre-filled with the email address used previously.

• Whether creating an account or using an existing one, specify https://sync-eol-fine.dev.mozaws.net as the custom server URL.

• Sync should start and successfully complete - let it do so.

• Via about:config, change the preference services.sync.clusterURL to

• https://sync-eol-soft.dev.mozaws.net/ - note that the trailing slash is important here!

• Via about:config, check if the pref services.sync.errorhandler.alert.mode exists. If it does, reset it (or set it to an empty string).

• I think you need to restart the browser at this point? ~Drew

The next time Sync starts, you should see the migration process kick off.

IMPORTANT: The sync migration UI will only be available after Sync starts for the first time. Don't expect to see any UI immediately after startup. Feel free to manually trigger sync to see this (but it should sync automatically ~10 seconds after startup) Debugging etc.

See https://philikon.wordpress.com/2011/06/13/how-to-file-a-good-sync-bug/ for info on how to get logs from Sync - these will be useful if something goes wrong. See also more details at https://wiki.mozilla.org/CloudServices/Sync/Client_Log_Debugging Current Testing Status

The try build at https://treeherder.mozilla.org/#/jobs?repo=try&revision=e61d95743567 should work as follows:

• The EOL from the server should cause a non-functioning info bar to appear on browser windows. This may show text and often may show "undefined" and has a non-functioning button - ignore this info bar.

• The "Sync Preferences" pane (in-content only for now) should show a (unstyled) yellowish bar at the top of the panel with an "upgrade" button. This button should ask you to create a FxA account, and once done, will change to reflect the "unverified" state. The "resend" button doesn't appear to work - I never tried the "forget" button - let me know if it doesn't ;)

• There's no "success" notification - it "just works". Go so sync options and check you are configured for FxA.