1Password does not work with Firefox 15

Firehawk

"We couldn't detect the 1Password application" error using 3.8.20.



Was working fine in previous versions, but not after the automatic upgrade to Firefox 15 a day or so ago. Continues to work with Safari and Chrome.



I'm guessing it has something to do with changes made in the beta last month concerning Firefox memory leaks, but not in the current "official" release 3.8.20. See [url="https://bugzilla.mozilla.org/show_bug.cgi?id=719601"]https://bugzilla.moz...gi?id=719601[/url] for that that issue.



Using Mountain Lion.



I have attempted reinstalling the FF browser extension from the 1Password app, but to no avail.

khad

Let's try [b]completely[/b] removing and reinstalling the Firefox extension. Other browsers handle the removal of the SQLite file automatically, but you will need to do this manually for Firefox:



1. In Firefox, select [b]Tools > Add-ons[/b] from the menu bar.

2. Click the [b]Remove[/b] button to remove the 1Password extension.

3. Quit Firefox.

4. In Finder, select [b]Go > Go to Folder[/b] from the menu bar.

5. Copy and paste the following path and press Return:



[CODE]~/Library/Application Support/Firefox/Profiles[/CODE]



6. Move the [font=courier new,courier,monospace][b]OnePassword.sqlite[/b][/font] file you see there to the desktop.



Then reinstall the 1Password extension in Firefox:



https://agilebits.com/extensions/mac/index.html



[i]Once everything is working well, you can safely move the [font=courier new,courier,monospace][b]OnePassword.sqlite[/b][/font] file on the desktop to the trash.[/i]





If you're still having trouble, could you please send us a Diagnostics Report?



In 1Password 3.8, just select [b]Help > Troubleshooting > Diagnostics Report[/b] from the menu bar.



Then attach the entire file to a private support ticket:



http://support.agilebits.com/discussion/new



Please include a link to this thread in order that we might more quickly "connect the dots" when we see your Diagnostics Report.



[color="#FF0000"]Please do not post your Diagnostics Report in the forums, though.[/color]



Looking forward to getting this resolved for you.



Cheers,

Firehawk

That got Firefox to recognize 1Password.



However, now I am affected by the common "connecting" issue that periodically affects Safari, Chrome and Firefox users. Restarting the helper does nothing.



It seems that when Agile started using the "helper" system, 1Password just became unreliable after being trouble-free for years. I no longer have the red1 issue on Safari, but now Firefox 15 functionality is completely broken.



And on all browsers upon opening, under Snow Leopard and previous OSs, the 1Password app used to jump to the correct item as open in the browser. Not any more. Now, I need to scroll and hunt for it when using any browser.

khad

The Helper is required since browsers have changed over the years and the extensions are now completely sandboxed. The extensions communicate with the main app via the Helper which uses an encrypted and authenticated [url="http://en.wikipedia.org/wiki/WebSocket"]WebSocket[/url] connection (a W3C standard). The old way of doing things is simply not feasible any more.



The vast majority of users have no problems, and I'd love to add you to that number. If you're still having trouble, could you please send us a Diagnostics Report?



In 1Password 3.8, just select [b]Help > Troubleshooting > Diagnostics Report[/b] from the menu bar.



If you are using 1Password 3.9 (from the Mac App Store), you'll need to follow the instructions here:



http://support.agilebits.com/kb/troubleshooting/create-a-diagnostics-report-to-help-agilebits-help-you



Then attach the entire file to an email to support AT agilebits.com.



Please include a link to this thread in order that we might more quickly "connect the dots" when we see your Diagnostics Report in our inbox.



[color="#FF0000"]Please do not post your Diagnostics Report in the forums, though.[/color]



Once we figure out what is blocking the Helper on your machine and resolve it, you shouldn't have to worry about it again. <img src='http://forum.agilebits.com/public/style_emoticons/<#EMO_DIR#>/smile.png' class='bbc_emoticon' alt=':)' />



Cheers,