How much time will it take for Google to finish its review for a extension before it gets published to the Chrome Web Store?
Review times vary; some reviews complete in a few hours, others take many days, and in some cases a review can take several weeks
https://developer.chrome.com/webstore/faq#faq-listing-108
Long time no review, many days, few weeks. Our users can't wait. This is reason why we moved almost feature of extension from Chrome Extension to our own app
So it's weird. The review now take 10 days because they review all versions like its new. So if you make a push and have a small fix it's another 10 days. And sometimes it is more than 10 days.
This means a different strategy towards trying to get your extension deployed. First we are setting up a testing item in the Chrome Store Dev Section so that we can test our extension extensively in Chrome.
Second we are looking at using eval() in order to put our code in a wrapper. We already do this for FF and Safari. The real goal is to move more and more of the processing to the back end so that the need for a deployment becomes rarer.
This sounds like a lot of hoops but if you look at it from Chrome's end and the issues they have had around people doing bad things with extensions this is the price that has to be paid in order to be able to make extensions from their point of view.
Related
I have a chrome extension, and I am creating a website for it, that has info, and a way to test it. I would like to show the number of users currently, but have found no way to do this. It doesn't have to update every day, but if it updated weekly that would be great!
Also- I don't care if it is by a outside company rather than chrome itself. all that matters is that it works.
I am planning to show something similar on my extension's site so I have googled around a bit recently. I found a repo (https://github.com/petasittek/chrome-web-store-stats) that parses information about extensions in the Chrome Web Store. It could be useful for you. I think I will end up just parsing the Webstore page for the user numbers everyday in save it to a database. My extension is also available for Firefox and I will do the same there then aggregate the results.
We're trying to work out how to resolve this issue, the current issue we have is our extension works on a unlimited amount of websites 1 of the features is a time & screenshot monitor so employer can track freelancers work other feature is ability to highlight text on any site and run a amazon search for the highlighted text for example.
We are always updating and any issues got fixed within 24-48 hours now with this happening every time we have to wait 1-3 weeks for a review according to google devs.
If we change the manifest to specific websites only then 99% of the time our extensions not going to work on all the other sites not listed. Can we do something else?
IF ANYONE HAS A SOLUTION OF WHAT WE CAN CHANGE TO MAKE THIS WORK I'M ALL EARS!
I have no previous experience with programming Google Chrome plugins which is why I am starting here to see if what I want to accomplish is possible/reasonable. I do however have a pretty broad experience in programming in general.
What I want:
I want some kind of "trigger" to go off when a new Chrome Notification (you know these little pop ups above the system tray) is popping up. I want to execute some script/code depending on what information the notification contains so that I for example could have an alarm go off if I receive an email from a certain user with a certain key word in the subject and get a pop up from my Gmail Notifier extension.
This is however just an example and I have a bunch of ideas for different notifications from different extensions and websites so don't get caught up on that particular example.
When I look at the Chrome Notification API I see that there is a getAll method that supposedly is getting all the "notifications in the system" but I do not find any Event for new notifications.
I suppose a possibility would be to poll with getAll a couple of times per second (it needs to be really fast for some implementations I have in mind) but it feels very tacky.
Is there any way to easily access new Notifications programmatically in Chrome?
(I'm open to all solutions, programming languages and such...)
Well, I searched long and hard and got involved with the Chromium dev group and asked around there. As far as I could figure out there was no reasonable way of accessing all Notifications programatically.
So what I ended up doing was just download the source-code of Chromium and build my own custom version of chromium adding a very crude API. Worked like a charm and not as complicated as one might think.
Cheers!
We run a fairly popular chrome extension with 200K+ installs and 70-90K active users (according to chrome webstore reports)
We have noticed that our numbers have started dipping in the past two months, despite a steady stream of hundreds of new daily installs. These numbers are different but broadly correlate with our Google Analytics numbers.
We suspect that some fraction of our installs are not being working, either because of some browser version-specific bugs or because it is being blocked by an anti-virus.
How do we know for sure? There doesn't seem to be some easy error reporting that we can rely on and the only other option seems to involve trying different versions and anti-viruses to see if this is true. Is there a better method?
Provide an after-uninstall form (using chrome.runtime.setUninstallURL - since Chrome 41) where a user can select the reason for uninstalling. Some extensions (ZenMate, for example) do it.
I've been running into this problem with odd regularity. Code working fine, and then it starts taking a couple minutes to save or load. It's about 2000 lines, so only on the larger-side of average. Well this problem found its way into my day today again, and I finally found the cause.
It turns out that all of my "slow code" had been copy and pasted, generally when I've used Select All. I've been doing this as I deploy the apps to coworkers and the like, causing a far amount of frustration.
I know this may sound obvious, but it seems the best practice for installing apps into other accounts is to share the script at viewer level and then make a copy.
I've also gone back to other slow code, tracked down a good version and made a copy and updated bit by bit. Slow code now fast.