Note

• Unable to reproduce issue on RC and Beta builds since the welcome to Firefox tour page is loaded right after loging in with firefox account
• In Nightly the first run page does not have the Sign in with Fx account option

Affected versions

• 60.0esr
• 60.5.1esr

Affected platforms

• Windows 10x64
• Ubuntu 18.0x64
• MacOS 10.12.6

Steps to reproduce

1. Launch Firefox with a new profile
2. Enter email on the first run page to login with firefox account
3. Click Continue button
4. Enter password on the next page
5. Click on "Open Gmail" to confirm the firefox sign in account
6. Confirm the sign in from email
7. Click on the first run page

Expected result

• First run page is refreshed after user signs in with Firefox sync account and about:newtab page should be displayed

Actual result

• First run page is empty after signing in with Firefox sync account and the account is verified by email

Additional notes

• In order to reproduce this scenario the Confirm Firefox Sign in from email is required

Sounds like bug 1500114?

(In reply to Julien Cristau [:jcristau] from comment #1)

Sounds like bug 1500114?

It does. Gabi, is this the same issue?

(In reply to :Gijs (he/him) from comment #2)

(In reply to Julien Cristau [:jcristau] from comment #1)

Sounds like bug 1500114?

It does. Gabi, is this the same issue?

It seems that this is the same issue. Followed the steps from bug 1500114 and the first run page is displayed as blank after updating Firefox, the difference is that after updating, the first run page is populated with the email address used for sync and it only becomes blank after hitting the Sign in button. Attached a gif with the end result.

(In reply to Gabi Cheta [:Gabi] Release Desktop QA from comment #4)

(In reply to :Gijs (he/him) from comment #2)

(In reply to Julien Cristau [:jcristau] from comment #1)

Sounds like bug 1500114?

It does. Gabi, is this the same issue?

It seems that this is the same issue. Followed the steps from bug 1500114 and the first run page is displayed as blank after updating Firefox, the difference is that after updating, the first run page is populated with the email address used for sync and it only becomes blank after hitting the Sign in button. Attached a gif with the end result.

OK, so this seems different... are there errors in the browser console when this happens?

(In reply to :Gijs (he/him) from comment #5)

(In reply to Gabi Cheta [:Gabi] Release Desktop QA from comment #4)

(In reply to :Gijs (he/him) from comment #2)

(In reply to Julien Cristau [:jcristau] from comment #1)

Sounds like bug 1500114?

It does. Gabi, is this the same issue?

It seems that this is the same issue. Followed the steps from bug 1500114 and the first run page is displayed as blank after updating Firefox, the difference is that after updating, the first run page is populated with the email address used for sync and it only becomes blank after hitting the Sign in button. Attached a gif with the end result.

OK, so this seems different... are there errors in the browser console when this happens?

Hello, so far I was not able to get the logs from browser console because the the email confirmation is not requested at sign in, tried this with a lot of Firefox accounts. I will return with the logs as soon I manage to reproduce the issue.

Here's the logs from browser console while reproducing the issue: https://pastebin.com/txQf4E9E
Note that the last error is logged in the browser console after refreshing the first run page:

Unexpected error appDependencies.bundle.js:74:98340
wrapMethod/t[e] https://accounts-static.cdn.mozilla.net/bundle-915bf7333fcc6033a96852727fcf87da72be0227/appDependencies.bundle.js:74:98340
error https://accounts-static.cdn.mozilla.net/bundle-915bf7333fcc6033a96852727fcf87da72be0227/app.bundle.en.js:1:45785
captureError https://accounts-static.cdn.mozilla.net/bundle-915bf7333fcc6033a96852727fcf87da72be0227/app.bundle.en.js:9:30093
captureAndFlushError https://accounts-static.cdn.mozilla.net/bundle-915bf7333fcc6033a96852727fcf87da72be0227/app.bundle.en.js:9:30245
fatalError https://accounts-static.cdn.mozilla.net/bundle-915bf7333fcc6033a96852727fcf87da72be0227/app.bundle.en.js:9:30594
fatalError https://accounts-static.cdn.mozilla.net/bundle-915bf7333fcc6033a96852727fcf87da72be0227/app.bundle.en.js:1:22708
Invalid chrome URI: /
Invalid chrome URI: /
Unexpected error appDependencies.bundle.js:74:98340
Attempt to set a forbidden header was denied: Connection 28503439-lcs_client_bin.js:134:386

Moving provisionally to FxA, so the content server peeps can take a look, but please recategorize if it's a bug in WebChannel, first run specifically, or anything like that.

(In reply to Gabi Cheta [:Gabi] Release Desktop QA from comment #7)

Here's the logs from browser console while reproducing the issue: https://pastebin.com/txQf4E9E
Note that the last error is logged in the browser console after refreshing the first run page:

Unexpected error appDependencies.bundle.js:74:98340
wrapMethod/t[e] https://accounts-static.cdn.mozilla.net/bundle-915bf7333fcc6033a96852727fcf87da72be0227/appDependencies.bundle.js:74:98340
error https://accounts-static.cdn.mozilla.net/bundle-915bf7333fcc6033a96852727fcf87da72be0227/app.bundle.en.js:1:45785
captureError https://accounts-static.cdn.mozilla.net/bundle-915bf7333fcc6033a96852727fcf87da72be0227/app.bundle.en.js:9:30093
captureAndFlushError https://accounts-static.cdn.mozilla.net/bundle-915bf7333fcc6033a96852727fcf87da72be0227/app.bundle.en.js:9:30245
fatalError https://accounts-static.cdn.mozilla.net/bundle-915bf7333fcc6033a96852727fcf87da72be0227/app.bundle.en.js:9:30594
fatalError https://accounts-static.cdn.mozilla.net/bundle-915bf7333fcc6033a96852727fcf87da72be0227/app.bundle.en.js:1:22708
Invalid chrome URI: /
Invalid chrome URI: /
Unexpected error appDependencies.bundle.js:74:98340
Attempt to set a forbidden header was denied: Connection 28503439-lcs_client_bin.js:134:386

Hey :Gabi, I tried to replicate this on Mac OSX Firefox 60 ESR using the first-run page [1] with no luck. This also worked correctly when prompted to Confirm your sign-in. Looking at my browser logs I did not get any of the errors you have above. Are you still experiencing this issue?

[1] - https://www.mozilla.org/en-US/firefox/60.0/firstrun/