Our Chrome Extension was removed from the Google Chrome store (and Google Marketplace) and we didn't get any notification before hand that it was going to be removed, and didn't get notified that it was removed (or for what reason).
Our extension is FollowUp.cc (a growing company that depends on the extension)
One of our engineers started reverting changes and republished an older version of the extension in hopes that that may help. We're out of ideas.
Any help would be appreciated!
Related
Background
I've been using the crx-hotreload package to auto-reload my chrome extensions during development because it's annoying to have to click the refresh button on the Extensions page every time you make a change; however, this package doesn't work with MV3 because it uses the chrome.runtime.getPackageDirectoryEntry method, which seems to have been removed from chrome.runtime in MV3. I can't find documentation to confirm that it was removed, but it's not there when I try to use it.
Questions
Does anyone know how to get access to all the files in the extension directory in Chrome Extension Manifest Version 3?
Or generally, is there a better way that I can hot-reload my chrome extensions during development that would work for MV3?
This is one of many things based on DOM capabilities of background pages that are removed from ManifestV3 because service workers don't have DOM. For example, getPackageDirectoryEntry is using the old nonstandard FileSystem API in its returned value.
As to why, apparently the switch to service workers simplifies the internal source code in Chromium, even if it doesn't provide any real improvements for extension authors or users.
At this point all you can do is present a convincing use case and ask Chromium developers via https://crbug.com to implement an alternative API.
I am using direct upload to Google Chrome Store via Webstore Developer Dashboard. I uploaded yesterday and it was published at night. This morning my colleague switched on his mac, opened Chrome, waited for 20 minutes, but extension was not updated. I did the same and my extension was updated.
What can it be? Are there any tweaks to make installed extension be up-to-date instantly? We do not want our users to use different versions of our extension.
There is a period of a few hours to a week where users could be using the old version of your extension. There isn't really anything you can do about it.
could someone help me with finding a place (URL, RSS feed or something else) where I could find what changes will be done in chrome extension API in each new Chrome release. It will be very useful to have that information before release to prepare extension.
Thanks!
This should be the 'source of true' for Chrome extensions (APIs and other important topics around it) - http://blog.chromium.org/search/label/extensions
I have an extension in the Chrome Webstore with ~400 000 users. Since a couple of months ago I have been getting e-mails from users whose extension has stopped working for them. They're basically just seeing the HTML page in the popup and options page. No content dynamically added by any JavaScript. After some helpful debugging from one user it appeared that the JavaScript files were gone. He sent me the following screenshot:
So what appears to happen is that the JS files become unreachable, or disappear. My guess is that this happen when an upgrade occurs. I haven't moved or changed the names of any files in any recent updates. No big changes have occurred at all.
I have solved this by sending instructions on how to find the extension on the hard drive, and attaching the extension files, so they manually themselves have to patch the extension. This always works. Now today, after receiving 4 e-mails within an hour with the same problem, I've had enough.
One user had all her extensions stop working at the same time. My guess being that this problem was the culprit. Me sending the patch to her solved the issue for my extension at least.
So my question to stackoverflow is: Has anyone else experienced this? This seems like quite a serious issue with Chrome. It started appearing around Chrome 20 and still happens with 22. My manifest version was prior to a couple of days ago 1.
The extension in question: http://chrome.google.com/webstore/detail/pnjaodmkngahhkoihejjehlcdlnohgmp?hl=en.
I built a quick one-off chrome extension about a month ago during the SOPA craziness. Long story short, it unblacked Wikipedia, so that people who needed it could get some work done.
Once the blackout was over, I updated the app to no longer have any effects on any websites. I also modified it so it would put a console.log() saying essentially "The blackout is over. SOPA is still important, but you should uninstall this extension".
Unfortunately, a month later, I'm still showing that 90% of the original users have the extension installed. Certainly it doesn't have that large of a footprint, but as a developer I feel it's my duty to not let my extension become crapware on my user's computers.
Is there a way to forcefully uninstall a chrome extension? Is there some way that would be unintrusive to the user that I could inform them that they should uninstall the extension?
You can update the extension so that it requires the 'management' permission, and then use chrome.management.uninstall to make the extension uninstall itself.
In my opinion, there is no way in this situation. Unless
If your extension makes a request to a server that you can access, such as a web service from you, maybe you can send an alert to your users.
If auto update is enabled in your extension, you can update your extension. In your updated version, you can show users an alert (shouldn't be a real javascript alert. Some kind of alert) to uninstall your extension.
If auto update is enabled, you may update your extension to do nothing. Just a console.log message.