I have a Chrome extension in the Chrome Webstore. I noticed a difference between the stats showing in old and new developer dashboard.
In the old developer dashboard, the stats view shows 3 installs on 28th of January, and 1 install on the 30th.
While in the new dashboard, it shows 5 installs on the 28th, and 3 installs on the 30th.
How are they calculated, why are they different and which one is accurate?
Related
I tried taking the print preview of a summary page which is an end product of the website I'm working on and it was working fine in the past since older versions of browsers were working fine with it. For instance it worked fine with version 78 of google chrome but any latest versions like 109 google chrome version didn't give correct result. The old version was able to give whole page content in the print preview while latest browser versions of google chrome, mozilla, brave was not giving the full content of the page. Its as if the content is getting trimmed off after a certain range of content .
I tried from certain past solutions like setting overflow:visible, setting display:block etc in scss file but none seemed giving the whole content in print preview.
When I navigate to my Azure static web app using Chrome I'm suddenly seeing an old version from months ago. It seems that several others have had this issue over the years (e.g. here), but I couldn't find any definitive solution anywhere.
Things I've tried:
Disabling cache in 'Developer Tools' on Chrome then right-clicking on the refresh button and selecting 'Empty cache and hard reload'. This lets me see the latest (correct) version of the site ... but once I navigate away and return I get the old version again.
Using Chrome incognito mode. This gets me the latest (correct) version of the site.
Using my phone, or using another non-Chrome browser also gets me the latest (correct) version of the site.
Unsetting my custom domain as the default for the site (under Settings > Custom domains) then navigating to the site's azurestaticapps.net address gets me the latest (correct) version of the site.
It seems that some sort of caching is going on when using my custom domain, but I can't seem to fix it. Interestingly, the version of the site that I'm seeing was a version from months ago when I last used that custom domain. Back then I'd linked the custom domain to a different version of the static web app launched under a different azurestaticapps name.
In our product we force install the Chrome extension we ship via Policy setting ExtensionForceInstallList. The setting is in the proper format and initially installs our Chrome extension from the Google web store just fine.
The problem is when I publish a newer version those same clients do not pull down the new version unless our tester goes to the Manage Extensions page and clicks Update.
These were on clients that brought up the Chrome browser today (a Tuesday) on a Chrome extension that was formally "published" on the previous Friday.
My Chrome extension is distributed through the Chrome store, which is supposed to manage the auto-update itself and push it after a few hours to my users.
I pushed an update more than one week ago and it seems that is hasn't been pushed to any user. The Chrome store is displaying the latest version number, but browsers are just not updating.
I know how to force my browser to update but I want the update to push to all my users.
Is there any thing I'm missing? Thanks!
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.