-
Notifications
You must be signed in to change notification settings - Fork 14
Latest version 1.3.0 no longer works #1
Comments
i am sorry,the api change to CacheClear. because chrome has the Cache api.
------------------ 原始邮件 ------------------
发件人: "DanLuczywo"<[email protected]>
发送时间: 2017年2月5日(星期天) 晚上9:46
收件人: "anrip/cordova-plugin-cache-clear"<[email protected]>;
抄送: "Subscribed"<[email protected]>;
主题: [anrip/cordova-plugin-cache-clear] Latest version 1.3.0 no longerworks (#1)
Have just built my app with the latest version and the call to window.cache.clear(clearCacheSuccess, clearCacheError); does not return so my app hangs.
Reverted to version 1.1.0 and all is well.
Have there been any significant changes to cause this?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
So how do I now use this plugin? |
Latest version of plugin is not working. It is not clearing the cache while using below code : function clearCache() { I tried while running the application. I have one button on Home screen to clearing the cache. So once user tab on ClearCache button, it will call the above function. I am getting the response in success but nothing is clearing from application web view. I have developed Hybrid Mobile application. That is running in iOS WebView. Please let me know what is the correct usage of the plugin and how? Thanks. |
I am having the same issue as @DanLuczywo. @DanLuczywo, from your example, it almost looks like you are using the other cache clearing plugin: https://www.npmjs.com/package/cordova-plugin-cache It is super easy to get these two confused. Long story short, both of them are hanging for me.
It is able to call the CacheClear.js function just fine... but never calls back. |
please use the 1.3.7 |
Have just built my app with the latest version and the call to window.cache.clear(clearCacheSuccess, clearCacheError); does not return so my app hangs.
Reverted to version 1.1.0 and all is well.
Have there been any significant changes to cause this?
The text was updated successfully, but these errors were encountered: