5 Mar 2013 10:30 AM #21
5 Mar 2013 11:18 AM #22
I mean the http headers,
it should serve it with mime type: text/cache-manifest
5 Mar 2013 12:18 PM #23
5 Mar 2013 12:25 PM #24
yeah, ms has some default mime type .. but what's the extension of your manifest file? It has to be .appcache, since you can't override .manifest on ms.
just double checking, other then that no idea other than adding some console or alerts to debug the microloader code, which is actually straight forward.
5 Mar 2013 12:41 PM #25
13 Mar 2013 11:35 AM #26
I came across this debugging tool JSConsole. I believe it may be able to shed some light on this issue. In your applications touch/microloader/production.js file there is a function called checkForUpdate. You can place console log statements in this function, build your application and using your devices web browser and JSConsole on your desktop browser, you can receive these log messages. You will have to update your devices application to one with these log statements at first. Subsequent update attempts you would receive messages to JSConsole.
By doing this you can see what is going on in the microloader and determine its role in this issue. I have attached step by step instructions.
I hope this helps.