This is a staging forum for AgileBits, not an official support forum. Visit http://discussions.agilebits.com instead.

CRX_FILE_NOT_READABLE error when attempting to install the 1Password extension in Chrome

dteare
dteare Agile Founder
edited February 2013 in Knowledge Base & FAQs

The latest version of Chrome changed how extensions are installed, and sometimes during installation Chrome will report the error "Package is invalid: 'CRX_FILE_NOT_READABLE'".

CRX_FILE_NOT_READABLE

This appears to be a regression in Chrome and multiple issues have been reported to the Chrome team.

Google is working on resolving these issues. In the meantime, there are some potential workarounds to get the installation working; here they are in order of simplicity:

1. Restart Chrome and then Download the Extension Manually

Try quitting Chrome, restarting, and then copy and paste the following link into Chrome's omnibar:

http://cdn.agilebits.com/dist/1P/ext/1Password.crx

Please note that clicking a link to the extension in Chrome does not work as reliably as copying and pasting, so please be sure to copy and paste.

2. Download Using Safari

If you are still having trouble, let's try downloading the file from Safari and then installing it from your system rather than over the network.

  1. Open Safari (not Chrome).
  2. Click this link in Safari to download the CRX file.
  3. Open Chrome.
  4. Use the File > Open File menu within Chrome to open the CRX file you just downloaded and install it in Chrome.

3. Clean Up Your Downloads Folder

This Chrome issue states that this bug is caused by the download not properly being renamed. Thus it conflicts with older files in your Downloads folder. The workaround follows.

  1. In Chrome, select Window > Downloads from the menu bar
  2. Click the "Open downloads folder" link in the upper right of the downloads list. This will open a Finder window where you'll see all your downloads there.
  3. Delete all the 1Password extension files that you see listed in your Downloads folder in Finder.
  4. Try installing the extension again: https://agilebits.com/extensions/mac/index.html

If you're still having trouble, please ensure that you have a Downloads location set within Chrome's preferences. You'll need to click the "Show advanced settings" link at the bottom of Chrome's settings list to reveal the correct option:

Then set (or reset) the "Download location" to /Users/yourusername/Downloads and try installing the extension again.

4. Rename the Extension File

In most cases one of the above steps will work around the issue, but in some stubborn cases, Chrome will continue to refuse the installation. Thankfully a commenter posted a workaround in the Chrome issue above:

After moving the CRX file to another folder, rename it to a random file name like ushasdfkjesd.crx, and drop it into Chrome. Then you should be able to install it without error.

To do this, download the extension (here's the link again) in Safari, open the downloads popover, and then click the magnifying glass to reveal the file in Finder, as shown here:

Open 1Password extension in Finder

When Finder opens, the 1Password.crx file will be highlighted. Press and hold the Option key, and then click on the 1Password.crx file. This will highlight the 1Password part of the name, allowing you to rename it. Call it anything you like and then press the return key to complete the rename. Now drag and drop the newly named file onto an open Chrome window.

5. Cleaning up Chrome's Settings

This step is a big one and not for the faint of heart: a few users reported that nothing worked until they cleared out Chrome's settings files and started over. It appears some of their settings files were corrupted or incompatible with a new Chrome version.

You can try this by quitting Chrome then opening Finder, selecting the Go > Go to Folder menu, and entering this path:

~/Library/Application Support/Google

You can then rename the Chrome folder (do not delete as all your bookmarks and other data are in this folder and you might decide you want them back someday). Now start Chrome and install the extension again.

Flag