Unanswered: No update message on production build after updating sdk
I have an application that was originally developed with sencha 2.0.1 and it runs inside a webview on Android. After updating to 2.1 sdk I didnt get the update message anymore because of the change on the manifest file name (I did add the mime type to my server). So we decided to rename the manifest file to cache.manifest again (and did the same on the reference on index.html). Which it works fine, or at least it seemed it was working fine.
We are now having some weird problems:
1 - In the version before the sdk update (say version 1) we had a button that had an arrow with a certain style defined on app.scss which included and image from our resources. We changed that button style and the image (by replacing the old one, we even tried renaming the new image) on version 2 (the one with sdk 2.1). But both arrows show at the same time. So this old image doesnt exist anymore, and there is no code referencing it but it just keeps showing. If you do a fresh install and run version 2 this doesn't happen, only when updating from version 1 to 2.
2 - After a lot of QA all devices we have were updating properly from version 1 to 2. But now some of our clients dont get the update message and they are still running version 1. But the version got corrupted and only shows the toolbar in the top and the rest is blank. App still does all background processing I would expect it to do, so its just the UI not showing (another strange problem with the css?)
3 - QA did noticed that it was not possible to go back from version 2 to version 1 on Android 4.0.4 if u hadn't run version 1 prior version 2. Application would behave in the same way as mentioned above, only toolbar showing.
These problems only happen when running inside a webview (except for number 2 that we don't know as we cant reproduce it, only our clients). And all seems to be related with a corrupted cache. Also Im using full update not delta.
Some questions that could help me to find the problem are:
1: Should the update have worked having different manifest file names? Or it was just not meant to be possible to do that?
2: Is there any documentation that deeply describes how the sencha update process works? Does it takes care of removing old files?
3: Is there a way i can force Ext.loader to remove all the cache and download all the files all over again?
4: Why the unique number on the cache.appcache file doesn't change when I do a change (an even my co-workers get the same number when they do a production build) but still I get the update message? I though the change on the manifest file will fire the cache update.
Thanks for reading and for your help
I have just realized I can reproduce all this problems even on the desktop browser by just clicking no when I received the update message. But it gets fixed the next time I run it.
You are also no deleting old unused files from the local storage, which at some point will end up exceeding the local storage maximum size, which might result on new files not having place to be stored and so application will fail
Tags for this Thread