This question is locked. New answers and comments are not allowed.
Hi,
I'm not entirely sure what's going on here, hard to troubleshoot as it's intermittent and happening only on users' devices, but I'm finding when we release a significant update to the app stores, we invariably get reports of random issues, errors and crashes which are invariably resolved by telling the user to restart their device. While this solution might be effective it hardly looks professional! Is there any way we can resolve this? I don't know a great deal about the inner workings of Cordova but it seems to me that the runtime is caching some of the JS files. I've tried appending a version number as a query string to the includes (e.g. script.js?v=10) which seemed to work for Android but Windows Phone doesn't support this technique.
Is this a common problem? Is there a better solution than telling users to restart their devices after every update?
Thanks,
Rob
I'm not entirely sure what's going on here, hard to troubleshoot as it's intermittent and happening only on users' devices, but I'm finding when we release a significant update to the app stores, we invariably get reports of random issues, errors and crashes which are invariably resolved by telling the user to restart their device. While this solution might be effective it hardly looks professional! Is there any way we can resolve this? I don't know a great deal about the inner workings of Cordova but it seems to me that the runtime is caching some of the JS files. I've tried appending a version number as a query string to the includes (e.g. script.js?v=10) which seemed to work for Android but Windows Phone doesn't support this technique.
Is this a common problem? Is there a better solution than telling users to restart their devices after every update?
Thanks,
Rob