تلاش سپورٹ

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

مزید سیکھیں

Firefox 29+ (new) Sync won't work at all on Firefox 30 Aurora, Website works fine in Chrome

  • 16 جواب دیں
  • 26 میں یہ مسئلہ ہے
  • 1 دیکھیں
  • آخری جواب بذریعہ DevilishDB

more options

I've tried to set-up the new sync with Firefox 30 Aurora, but it won't work since the sync page just displays a blank box. Inside this box is an iframe pointing to some location like accounts.firefox.com, which when viewed in Aurora still is blank, but in Chromium I can sign up and in general it works fine. This means that now, I've got an account, but I can't actually set-up sync on Aurora because the sync page is blank.

I've tried to set-up the new sync with Firefox 30 Aurora, but it won't work since the sync page just displays a blank box. Inside this box is an iframe pointing to some location like accounts.firefox.com, which when viewed in Aurora still is blank, but in Chromium I can sign up and in general it works fine. This means that now, I've got an account, but I can't actually set-up sync on Aurora because the sync page is blank.

منتخب شدہ حل

Yep, the bug with their server-side settings has been fixed now, so it works!

اس جواب کو سیاق و سباق میں پڑھیں 👍 0

تمام جوابات (16)

more options

You'll have to keep in mind that the Aurora builds is not yet fully stable and ready for even beta release. You hence should expect some problems.

more options

Try again see if it works now it should do. Aurora is pretty stable.

All you are doing is trying to initially access an ordinary webpage https://accounts.firefox.com/signup

Make sure you have javascript enabled and it is not blocked by anything. If necessary clear the cache and cookies and try again

more options

P.S. the ordinary work flow would be to use the menu buttons and that opens a page about:accounts you may navigate to that directly by keying into the addressbar about:accounts

more options

I've tried through the menu (about:accounts) and accounts.firefox.com, neither work and I've also cleared the cache and localstorage. Plus, I've tried disabling all extensions and that didn't work either (with restart). So, I'm not exactly sure what's wrong...

more options

I tried myself from Aurora and it is not working for me but I get a specific error.

I see

Use of getPreventDefault() is deprecated.  Use defaultPrevented instead. 8f998cda.main.js:3
 Use of getPreventDefault() is deprecated.  Use defaultPrevented instead. 880ec6c3.firefox.png

Personally I am not too interested in Sync. I am not sure I will troubleshoot this as I guess I would need disposable email accounts to do that.


Initially I used a Ubuntu canonicaI build. Now I have also tried with Beta Mozilla fx29 and again it is not working. This time more like you see with a blank Iframe

I will have a go tomorrow and see what happens in a new install.

John99 کی جانب سے میں ترمیمکی گئ

more options

I got that too in the console but I think it's something to do with an extension, not sure. Anyway it's only a warning, not an error, i.e. "This will work but it's not a modern way to do it". Did you get a login/signup form at all? The problem is that nothing appears when I click 'get started'.

more options

Page is


 


<?xml version="1.0" encoding="UTF-8"?>
<!-- This Source Code Form is subject to the terms of the Mozilla Public
   - License, v. 2.0. If a copy of the MPL was not distributed with this
   - file, You can obtain one at http://mozilla.org/MPL/2.0/. -->
<!DOCTYPE html [
  <!ENTITY % htmlDTD PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd">
  %htmlDTD;
  <!ENTITY % brandDTD SYSTEM "chrome://branding/locale/brand.dtd">
  %brandDTD;
  <!ENTITY % aboutAccountsDTD SYSTEM "chrome://browser/locale/aboutAccounts.dtd">
  %aboutAccountsDTD;
  <!ENTITY % syncBrandDTD SYSTEM "chrome://browser/locale/syncBrand.dtd">
  %syncBrandDTD;
]>

 <html xmlns="http://www.w3.org/1999/xhtml">
  <head>
   <title>&syncBrand.fullName.label;</title>
   <meta name="viewport" content="width=device-width"/>


   <link rel="icon" type="image/png" id="favicon"
         href="chrome://branding/content/icon32.png"/>
   <link rel="stylesheet"
     href="chrome://browser/content/aboutaccounts/fonts.css"
     type="text/css" />
   <link rel="stylesheet"
     href="chrome://browser/content/aboutaccounts/normalize.css"
     type="text/css" />
   <link rel="stylesheet"
     href="chrome://browser/content/aboutaccounts/main.css"
     type="text/css" />
   <link rel="stylesheet"
     href="chrome://browser/content/aboutaccounts/aboutaccounts.css"
     type="text/css" />
  </head>
  <body>
    <div id="stage">

      <div id="manage">
        <header>
          <h--1>&aboutAccounts.welcome;</h--1>
        </header>

        <section>
            <div class="graphic graphic-sync-intro"> </div>

            <div class="button-row">
              <a class="button" href="#" onclick="openPrefs()">&aboutAccountsConfig.manage.label;</a>
            </div>
        </section>
      </div>

      <div id="intro">
        <header>
          <h--1>&aboutAccounts.welcome;</h--1>
        </header>

        <section>
            <div class="graphic graphic-sync-intro"> </div>

            <div class="description">&aboutAccountsConfig.description;</div>

            <div class="button-row">
              <a class="button" href="#" onclick="getStarted()">&aboutAccountsConfig.startButton.label;</a>
            </div>

            <div class="links">
              <a id="oldsync" class="no-underline" href="#" onclick="handleOldSync();">&aboutAccountsConfig.useOldSync.label;</a>
            </div>
        </section>
      </div>

    </div>

    <iframe mozframetype="content" id="remote" />

    <script type="application/javascript;version=1.8"
      src="chrome://browser/content/utilityOverlay.js"/>
    <script type="text/javascript;version=1.8"
      src="chrome://browser/content/aboutaccounts/aboutaccounts.js" />
  </body>
 </html>




N.B. edited with added ^hyphens^  ^pre^ & ^nowiki^ tags in attempt to display more accurately

I have not tried with a new install safe mode & plugins disabled. I will tag this as escalate, someone else will probably get back to looking at this before I do. In Canonical Fx30 I am getting the login etc form in Mozilla Beta Fx29 I am not.

John99 کی جانب سے میں ترمیمکی گئ

more options

Did you try to right-click on the page and use View Page Source to see if there is any code loaded?

Do you see any errors in the Browser Console (Firefox/Tools > Web Developer) about the about:accounts page?


Start Firefox in Safe Mode to check if one of the extensions (Firefox/Tools > Add-ons > Extensions) or if hardware acceleration is causing the problem (switch to the DEFAULT theme: Firefox/Tools > Add-ons > Appearance).

  • Do NOT click the Reset button on the Safe Mode start window.

Create a new profile as a test to check if your current profile is causing the problem.

See "Creating a profile":

If the new profile works then you can transfer files from a previously used profile to the new profile, but be cautious not to copy corrupted files to avoid carrying over the problem

cor-el کی جانب سے میں ترمیمکی گئ

more options

New update Fx29 with new profile all plugins disabled. As above. Not working to add sync.

I tried Nightly Mozilla Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0 ID:20140425030209 CSet: b836d89be72b that works fine and is able to use sync.

more options

Here is the issue I have posted on Github: https://github.com/mozilla/fxa-content-server/issues/1017

more options

The log in page is a frame with this URL for me in Aurora:

more options

I can use that directly to get the create page

I then get a red box saying

An attempt was made to use an object that is not, or is no longer, usable

But now I have a sync account for this machine the workflow will be different. This is a working profile. I will try with clean profile and attempting to sign in. I normally have noscript running and that may well interfere from this profile.

more options

Tried from a clean profile safemode with plugins disabled Canonical fx31 attempting to create a new sync account failed with red box

<div style="" class="error">Unexpected error</div>

I don't think I saw any JS errors only warnings. Also tried to register with existing account and again failed.

I have other work to do will come back to this some time tonight. Let me know if you have any other suggestions or questions. Personally I am not really interested in using Sync at present but will help if I can in investigating the problem.

more options

I saw another issue with the blank page: https://bugzilla.mozilla.org/show_bug.cgi?id=1001686 was the bug I filed. We need more info on this issue, can you please add the info to the bug too?

Current info needed:

  1. can you install httpfox add-on and click start, then attempt to load about:accounts
  1. what response code are you getting? Please paste anything you see for https://accounts.firefox.com
  1. Also, can you try loading this? https://accounts.firefox.com
more options

I was sure I had already made another two posts in this thread. I hope it is my memory playing tricks and not a forum issue.

DevilishDB

I hope the issue is now resolved for you using either the workaround in the Github issues thread or the new Sync Account fix ( Is that out yet  ?).

Thanks for reporting this it would appear it was an otherwise unnoticed bug

Everyone

Two potential issues here

  1. Sync Account login setup from about:accounts or from the new sync button needs the en-US language.
    • There is a workaround, add another language en-US to Firefox, however the Sync Accounts should now be fixed.
  2. The addon NoScript may cause problems. This is offtopic for the thread title but I noticed it whist looking at this. NoScript needs to be disabled or set to allow all scripts globally . It is not sufficient to set it to allow all this page Otherwise the initial new Sync signon process fails.
more options

منتخب شدہ حل

Yep, the bug with their server-side settings has been fixed now, so it works!