I recently got a Chrome Developer account, i paid the 5 bucks and stuff. I published my extension after extensive testing and it works perfectly, but after i uploaded the app an
It because you're hitting an edge case bug in Google which verifies at run time that the contents inside an extension on disk match what was uploaded to the web store (designed to prevent malicious software from spoofing legitimate extensions).
Three known such bugs are:
crbug.com/437675 (dot-slash paths in content scripts)
crbug.com/439464 (incorrect case in img tag injected by content-script)
crbug.com/444085 (having // instead of / as an interior separator inside a url)
Please look through all the details and correct your code properly. For example, for my experience with this issue I was running into crbug.com/444085 by ends up generating requests to at least two urls with double-slashes in them:
images//arrow.png
images//popup.png
Then I modified the lines in the "script.js" file where has script like:
.... imgURL + '/arrow.png' ....
.... imgURL + '/popup.png' ....
Since imgURL
already has a trailing slash in each case. Then the issue was fixed. Hope it helps.