Loading chunk 29 failed when trying to sign into Sync
Categories
(Cloud Services :: Server: Firefox Accounts, defect)
Tracking
(Not tracked)
People
(Reporter: dtorkelson, Assigned: jrgm)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
On iPad Mini, iOS 9.3.5, Firefox 8.3 (5826)
- Went to Settings > Sign In to Firefox
- Entered email address and hit Continue
Actual results:
Red box: "Loading chunk 29 failed. (missing: https://accounts-static.cdn.mozilla.net/bundle-1a060a9af79632342490bc2f1d109de6e3f62124/vendors~fxaClient.bundle.js)"
Expected results:
Asked for password
|
||
Comment 1•6 years ago
|
||
The priority flag is not set for this bug.
:garvan, could you have a look please?
For more information, please visit auto_nag documentation.
I'm one those impacted by this bug which appears to be happening at different chunks for different people (since January I've personally seen errors thrown for for chunks 23, 26, 29 and currently 30). There are also several bug reports that should probably be gathered up into a single bug report - see also:
https://bugzilla.mozilla.org/show_bug.cgi?id=1582748
https://bugzilla.mozilla.org/show_bug.cgi?id=1614784
https://bugzilla.mozilla.org/show_bug.cgi?id=1582748
I don't think I have relevant experience for fixing the bug (I've got some python experience, but minimal js). However, I'm happy to spend some time on tracking down the issue and testing solutions if I'm given a bit of direction. My system info:
- Firefox sync on Windows 10. Working fine on two PCs.
- Firefox sync on IOS 9.3.6, iPhone and iPad, not working.
- My partner is using IOS 13 on a iPad. Sync working fine there.
Cheers,
Larry
Moving this to cloud services, I don't think the bug is on the client-side.
|
||
Updated•5 years ago
|
Latest update for IOS 9.3.6 - Hitting "Sign in to firefox" goes to a loading animation and the message "Could not load page". No further information provided.
Cheers,
Larry
|
||
Comment 5•5 years ago
|
||
You're right, there are several of these bugs with different chunks. We still don't have a way to reproduce this error. I will consolidate the reports into one bug.
Description
•