You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm happy to make a PR, although I'm not sure what the best thing to do is.
Looking at their docs, it sounds the property might be unnecessary if you're sending it straight to the chrome web store.
So, an extra question asking for the url, or just some content in the docs explaining that you might need to add this to package it properly. (it's quite hard to find the solution from the error message)
The text was updated successfully, but these errors were encountered:
update_url is not a mandatory option in almost cases as I understand. About autoupdate? Sadly, any content for chrome extension, we hardly depend on docs on Chrome developer site. If you can feel that a lack of content, you should ask them to update.
OK. I don't know how common it would be. But I think that following yeoman's current documentation to package the app with gulp package results in the error every time when you install the result in chrome directly. Which suggests something should be changed here, no?
If you want to install the extension from local? You don't need to do package, which is for the market place. I recommend you can try to zip the extension with source files
When packaging the extension locally, you get the error mentioned in these links if you don't add the
update_url
:https://productforums.google.com/d/msg/chrome/kGgLwnrDKpQ/TFK1DG23BgAJ
https://stackoverflow.com/questions/47757849/chrome-extension-disabled-this-extension-may-have-been-corrupted-chrome-63-0-3
I'm happy to make a PR, although I'm not sure what the best thing to do is.
Looking at their docs, it sounds the property might be unnecessary if you're sending it straight to the chrome web store.
So, an extra question asking for the url, or just some content in the docs explaining that you might need to add this to package it properly. (it's quite hard to find the solution from the error message)
The text was updated successfully, but these errors were encountered: