1209481 - 'Sync encountered an error - see about:sync-log for the log file.' thrown in the Browser Console although sync seems to work

Status: RESOLVED INVALID

(Firefox :: Sync, defect)

Description

[Ada [:adalucinet]]

Reproducible with 41.0.1RC, 42.0b2, latest 43.0a2 and 44.0a1
Affected platforms: Windows 7 x64, Windows 8 x86, Mac OS X 10.10.4 and Ubuntu 14.04 x64

Steps to reproduce:
1. Launch Firefox and open the Browser Console, from menu [≡] → select "Developer" → select "Browser Console".
2. Log in to FxA via one of the available Sync buttons (e.g. about:home, about:preferences#sync, menu panel, Tools).
3. Keep an eye on the Browser Console.

Expected result: No errors displayed in the Browser Console.

Actual result: 'Sync encountered an error - see about:sync-log for the log file.' thrown by policies.js:692:0 is displayed in the Browser Console.

Additional notes:
1. The above sync error is intermittently thrown for various scenarios - please see the below logs:
- after changing password → https://goo.gl/Dsa8xg 
- after log in with an existing account → https://goo.gl/np3F8V
- after sign up → https://goo.gl/PwaoX8
2. Not reproducible with 40.0b9 - will investigate further for the regression range

Comment 1

[Mark Hammond [:markh] [:mhammond]]

(In reply to Alexandra Lucinet, QA Mentor [:adalucinet] from comment #0)
> Actual result: 'Sync encountered an error - see about:sync-log for the log
> file.' thrown by policies.js:692:0 is displayed in the Browser Console.

Thanks!

Note we probably just want one bug per scenario, and because these logs are simply text files, it's probably better to just upload them as attachments rather than links to a google doc.

> Additional notes:
> 1. The above sync error is intermittently thrown for various scenarios -
> please see the below logs:
> - after changing password → https://goo.gl/Dsa8xg 

I opened bug 1209499 for this.

> - after log in with an existing account → https://goo.gl/np3F8V
> - after sign up → https://goo.gl/PwaoX8

Both of these are bug 1195569.

> 2. Not reproducible with 40.0b9 - will investigate further for the
> regression range

It will be bug 1148980 - we now create an error log whenever an "ERROR" entry is written to the log (which is a tradeoff - before we may have missed some real issues because we didn't detect an error, but now we may write error logs when the issue is actually benign or somewhat expected)

Thanks for the report, but I'm going to close this and track the issues in the bugs mentioned above.