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.
Related
I can not make my self-hosted extension to update itself, neither automatically nor with manual updates.
I tried:
Update button at chrome://extensions/ with Developer mode enabled
Update button at individual extension page under chrome://extensions with Developer mode enabled
Of course before doing that I:
updated version number in manifest.json and updates.xml
made sure that extension ID in app appid and URL in updatecheck codebase are correct
The only way that worked is manually drag a file with new version to a tab with chrome://extensions/, both with and without uninstalling the older version first.
As a sidenote, the extension is installed in two of my different user profiles under the same installation of Chrome (and under the same MacOS user), but I would be surprised if it's relevant.
How can I debug the problem? What else can I check?
i've published a new chrome extension to the google chrome's web store, to my company account.
we already have few extensions there.
the extension's upload was completed successfully
and its status is "published"
uploaded it 3 days ago
in addition, I examined the manifest multiple times, and seems like I have all the relevant properties set there.
BUT, I can't see my extension available in the Web Store, nor find it in the search
any idea on what could be the problem ?
Make sure that your app is published as public to be visible to everyone. I think it usually takes a week for the app to be visible. You can also reach out to the Chrome team through their support page.
In other words - they got a new website and used the domain that was assigned to the old site.
When I google it or yahoo or bing it, on the three browsers on my Mac, I find the new website.
I think he's saying the old website still comes up. It's been a month. they're using I.E. not sure what version. He claims they're seeing the old site on pc's that have never before been used to view the old site, so the cache is not an issue.
I don't see how this is possible. Is this possible?
He may be having the old website's IP address cached. Ask the client to open command prompt and type ipconfig /flushdns.
I've deployed DotNetNuke 07.03.02 to Azure using Azure's own wizard - worked fine. Been using DNN for years on personal server without issues.
However, when I try to add a module to a page (i.e regular editing) DNN adds the wrong module to the page; seemingly FirstOrDefault from the list of installed modules.
I.E, I want to add the "HTML" module (or any other) to a page but instead I get the "Banners" module. If I then uninstall the the Banners module it now adds the "Modules list" module.
See below example, where I'm editing the "About" page of my site and have tried to add the HTML module.
I hope anyone with insight into DNN (on Azure) can provide info. I am a .Net developer, but have so far had no reason to dig into DNN's inner workings.
I made a fresh install of DNN on Azure and installed a skin. Works fine.
I notice the ribbon look different now, so I guess there's a new stable of DNN.
It works well anyway, so case closed.
I need to edit and then publish my Chrome extension. I know that it sometimes takes over an hour to publish an extension, but once it has been published, can I assume that all users are using this new extension version? Or might they still be using the old one for a while? And, if so, for how long?
I publish via the Chrome dashboard. Sorry if this is the wrong place to ask. I have tried searching through Chrome's documentation.
Issue: I need to update my server side code, but if a user is still using the old extension version, then it will fail very badly.
You should not make any assumptions about the extension update frequency. The update frequency is 5 hours by default. This value can be changed by the user through the --extensions-update-frequency flag. In practice, most users will stick to the defaults though. And do not forget that it is unreasonable to expect that all of your users have their computer online all the time.
You should keep the code for the old and new version at the server's side. If you haven't done before, include a version identifier in your request. This version identifier does not need to map 1:1 to your Chrome extension version; just use a value and keep incrementing it for every significant API update.
If you did not include a version identifier in your previous version, just assume that the user is using the old version if the version identifier is missing from the request, and consistently include the version identifier in requests from your new Chrome extension.
If you have set a minimum_chrome_version in your manifest file, then the user will also be stuck at an old version of your extension if they use an older Chrome version.
Though not relevant for your specific situation, extension authors can choose to distribute their extension to a specific percentage of users via the dashboard at the Chrome Web store. When this feature is used, you obviously have users who are still using the old version.
You have to handle in your code the possibility of users having the old version. Its not published how long that might be but from experience it can be a full day at least.
According to the docs and other sources the update happens within a few hours from publishing.
Every few hours, the browser checks whether any installed extensions or apps...
The default update check frequency is several hours,
I suggest you implement a mechanism to check the version of the extension making the request and if it is not current, either fallback to differently handling the request (based on the old server-side code), or inform the user they have to update (although I would not advice that, as it might scare and annoy users).
In order to force an update of one's extension:
but you can force an update using the Extensions page's Update extensions now button.
Basically, you have to go to the Extensions page, check "Developer mode" and press the "Update extensions" button that appears.
Bottom line
I would:
Implement a mechanism to include the version in a request
Maintain two code based on the server (for a few days only)
serve each request based on the version