New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to update extension due to an unexpected error #853

Closed
MichaelFedora opened this Issue Dec 16, 2018 · 2 comments

Comments

Projects
None yet
2 participants
@MichaelFedora
Copy link

MichaelFedora commented Dec 16, 2018

Describe the problem and steps to reproduce it:

  • Build extension (or use the already built zip)
  • Upload it
  • Get an unknown error while validating

What happened?

  • I want to update my Extension but am unable to due to FF AMO telling me that it was unable to verify "due to an unexpected error."

What did you expect to happen?

  • It uploads and verifies correctly

Anything else we should know?

Chrome web store took it just fine (it is a WebExtension-Api based extension with polyfills for Chrome as it doesn't use the browser interface).

This is the result I get:

image

I am able to load it via about:debugging just fine, though about:addons doesn't take it due to it not being signed (I assume AMO does that automatically?).

@diox

This comment has been minimized.

Copy link
Member

diox commented Jan 7, 2019

I assume it's because the linter chokes on the very large minified files your add-on contains. It does work locally on my machine, but it takes a significant amount of time and memory to process (more than 30 seconds and 1GB memory). It's probably hitting against memory or time execution limits in production...

@MichaelFedora

This comment has been minimized.

Copy link

MichaelFedora commented Jan 9, 2019

Good to know. I've implemented splitting chunks by using html-webpack-loader@next (4.0 beta) and moved my background script to the background html page. This reduced the uncompressed size by ~5mb and it went through flawlessly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment