Extension error: Failed to load extension

[Scott]

I have loaded my app from a local directory, but it disappears when I relaunch Chrome. The app persists after a relaunch if I rename the directory. Does anyone know what might be wrong?

Here is the log message:

[6764:4796:1101/132959:WARNING:extension_error_reporter.cc(79)] Extension error: Failed to load extension from: D:\foo\chrome-app\app.

If I copy the contents of that directory into D:\foo\chrome-app\a and D:\foo\chrome-app\b\app, after adding either of those directories as an app, they will successfully load after a relaunch of Chrome.

What problem could Chrome having with D:\foo\chrome-app\app?

[Antony Sargent]

Hmm, I wonder if there's any chance that your preferences file has a stale entry in it pointing at that directory. If you uninstall the development loaded extension and then shut down chrome, do you still see any reference to that path in your Preferences or Secure Preferences files?

You can find their location here:

https://www.chromium.org/user-experience/user-data-directory

--
You received this message because you are subscribed to the Google Groups "Chromium-extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To post to this group, send email to chromium-...@chromium.org.
Visit this group at http://groups.google.com/a/chromium.org/group/chromium-extensions/.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/4bbadeb8-0371-47a6-afbe-0da4af623062%40chromium.org.
For more options, visit https://groups.google.com/a/chromium.org/d/optout.

[Chuck Baker]

I was having a similar problem a while back. After loading the extension directory, the entire directory would get deleted.  It turns out that the problem was that I was using a non-ascii character in one of the filenames (it was the 'Ø' or utf-8 0x00F8).  I renamed the file to pure ascii and it worked fine.

Are your pathnames all ascii characters?