FunFetched Posted July 17, 2018 Share Posted July 17, 2018 I just updated my app the other day, and started getting reports of some users' Chrome browsers refusing to download and update .babylon files in their IndexedDB. Other browsers seem to have no problem at all, but Chrome, as I've learned, can be especially stubborn when it comes to caching. Before you ask, yes, I updated the version number in the associated .manifest files to no avail. After investigating the XHR requests in Chrome, I noticed that the .manifest file checks use a date-based query string for cache-busting, which works great. However, the .babylon file requests themselves were not. I changed the following... Database.prototype._saveFileIntoDBAsync = function (url, callback, progressCallback, useArrayBuffer) { ... xhr.open("GET", url + '?' + Date.now(), true); ... and now all is well. Apparently, Chrome (and only Chrome) was loading a cached file to put in the IndexedDB; putting a cached file into another cache, essentially. Nuts. Quote Link to comment Share on other sites More sharing options...
Guest Posted July 17, 2018 Share Posted July 17, 2018 I will be happy to merge the fix if you want to do a PR FunFetched 1 Quote Link to comment Share on other sites More sharing options...
FunFetched Posted July 17, 2018 Author Share Posted July 17, 2018 18 minutes ago, Deltakosh said: I will be happy to merge the fix if you want to do a PR Done! Quote Link to comment Share on other sites More sharing options...
Guest Posted July 17, 2018 Share Posted July 17, 2018 and merged Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.