https://community.intel.com/t5/Software-Archive/intel-xdk-cache-undefined-Cannot-read-property-clearAllCookies/m-p/1047620#M48616 <P>Based on the index.html file you are showing, I'm betting that the template you used includes an event called "app.Ready" that indicates that all DOM, legacy and Cordova read events have completed. Trigger on that event before you try to access any Cordova or XDK functions, the underlying native system needs to finish initialization before you can call that stuff.</P> <P>If it's the template I'm thinking of, there should be an xdk/init-dev.js file and there might be a js/init-app.js file and js/app.js file. The first generates the app.Ready event. The last two provide examples of how to init your code. Lots of comments in those files.</P> Sat, 14 Mar 2015 00:10:17 GMT PaulF_IntelCorp 2015-03-14T00:10:17Z https://community.intel.com/t5/Software-Archive/intel-xdk-cache-undefined-Cannot-read-property-clearAllCookies/m-p/1047618#M48614 <PRE class="brush:jscript;">&lt;!DOCTYPE html&gt; &lt;html&gt; &lt;!-- * Copyright © 2012-2015, Intel Corporation. All rights reserved. * Please see the included README.md file for license terms and conditions. --&gt; &lt;head&gt; &lt;meta charset="UTF-8"&gt; &lt;link rel="stylesheet" type="text/css" href="app_framework/2.1/css/af.ui.min.css"&gt; &lt;link rel="stylesheet" type="text/css" href="app_framework/2.1/css/icons.min.css"&gt; &lt;title&gt;Test App&lt;/title&gt; &lt;meta http-equiv="Content-type" content="text/html; charset=utf-8"&gt; &lt;!-- * The "meta viewport" tag (below) helps your app size appropriately to a device's ideal viewport. * Note that Windows device viewports work better when initialized using the @viewport CSS rule. * For a quick overview of "meta viewport" and @viewport, see this article: * <A href="http://webdesign.tutsplus.com/tutorials/htmlcss-tutorials/quick-tip-dont-forget-the-viewport-meta-tag" target="_blank">http://webdesign.tutsplus.com/tutorials/htmlcss-tutorials/quick-tip-dont-forget-the-viewport-meta-tag</A> * To see how it works, try your app on a real device with and without a "meta viewport" tag. * Additional useful references include: * <A href="http://www.quirksmode.org/mobile/viewports.html" target="_blank">http://www.quirksmode.org/mobile/viewports.html</A> * <A href="http://www.quirksmode.org/mobile/metaviewport/devices.html" target="_blank">http://www.quirksmode.org/mobile/metaviewport/devices.html</A> * <A href="https://developer.apple.com/library/safari/documentation/AppleApplications/Reference/SafariHTMLRef/Articles/MetaTags.html" target="_blank">https://developer.apple.com/library/safari/documentation/AppleApplications/Reference/SafariHTMLRef/Articles/MetaTags.html</A> --&gt; &lt;!-- &lt;meta name="viewport" content="width=device-width, minimum-scale=1, initial-scale=1"&gt; --&gt; &lt;meta name="viewport" content="width=device-width, minimum-scale=1, initial-scale=1, user-scalable=no"&gt; &lt;!-- &lt;meta name="viewport" content="width=device-width, initial-scale=1, user-scalable=yes, minimum-scale=1, maximum-scale=2"&gt; --&gt; &lt;style&gt; /* following three (cascaded) are equivalent to above three meta viewport statements */ /* see <A href="http://www.quirksmode.org/blog/archives/2014/05/html5_dev_conf.html" target="_blank">http://www.quirksmode.org/blog/archives/2014/05/html5_dev_conf.html</A> */ /* see <A href="http://dev.w3.org/csswg/css-device-adapt/" target="_blank">http://dev.w3.org/csswg/css-device-adapt/</A> */ @-ms-viewport { width: 100vw ; min-zoom: 100% ; zoom: 100% ; } @viewport { width: 100vw ; min-zoom: 100% zoom: 100% ; } @-ms-viewport { user-zoom: fixed ; min-zoom: 100% ; } @viewport { user-zoom: fixed ; min-zoom: 100% ; } /*@-ms-viewport { user-zoom: zoom ; min-zoom: 100% ; max-zoom: 200% ; } @viewport { user-zoom: zoom ; min-zoom: 100% ; max-zoom: 200% ; }*/ &lt;/style&gt; &lt;link rel="stylesheet" href="css/app.css"&gt; &lt;link rel="stylesheet" type="text/css" href="css/index_main.less.css" class="main-less"&gt; &lt;!-- IMPORTANT: Do not include a weinre script tag as part of your release builds! --&gt; &lt;!-- Place your remote debugging (weinre) script URL from the Test tab here, if it does not work below --&gt; &lt;!-- &lt;script src="http://debug-software.intel.com/target/target-script-min.js#insertabiglongfunkynumberfromthexdkstesttab"&gt;&lt;/script&gt; --&gt; &lt;!-- Recommended location for your JavaScript libraries --&gt; &lt;!-- These library references (below) are just examples to give you the general idea... --&gt; &lt;!-- &lt;script src="lib/mc/hammer.js"&gt;&lt;/script&gt; --&gt; &lt;!-- &lt;script src="lib/ft/fastclick.js"&gt;&lt;/script&gt; --&gt; &lt;script src="intelxdk.js"&gt;&lt;/script&gt; &lt;!-- phantom library, needed for Intel XDK "legacy" container api calls --&gt; &lt;script src="xhr.js"&gt;&lt;/script&gt; &lt;!-- phantom library, needed for Intel XDK "legacy" container CORS --&gt; &lt;!-- * cordova.js is a phantom lib for "Cordova HTML5 web app," it does nothing in a "Standard HTML5 web app" * Seeing a "Failed to load resource: net::ERR_FILE_NOT_FOUND" message caused by this "cordova.js" script? * The cordova.js script is required if you convert your "Standard HTML5" project into a "Cordova" project. * You can safely ignore the error or comment out this line if you will not be developing a Cordova app. --&gt; &lt;script src="cordova.js" id="xdkJScordova_"&gt;&lt;/script&gt; &lt;script src="js/app.js"&gt;&lt;/script&gt; &lt;!-- for your event code, see README and file comments for details --&gt; &lt;script src="js/init-app.js"&gt;&lt;/script&gt; &lt;!-- for your init code, see README and file comments for details --&gt; &lt;script src="xdk/init-dev.js"&gt;&lt;/script&gt; &lt;!-- normalizes device and document ready events, see file for details --&gt; &lt;!-- You may substitute jQuery for the App Framework selector library. See <A href="http://app-framework-software.intel.com/documentation.php#afui/afui_jquery" target="_blank">http://app-framework-software.intel.com/documentation.php#afui/afui_jquery</A> --&gt; &lt;script type="application/javascript" src="app_framework/2.1/appframework.js"&gt;&lt;/script&gt; &lt;script type="application/javascript" src="app_framework/2.1/appframework.ui.js" data-ver="1"&gt;&lt;/script&gt; &lt;script&gt; $.ui.autoLaunch = true; $.ui.useOSThemes = true; $.ui.animateHeaders = false; &lt;/script&gt; &lt;script&gt; $.ui.ready(function() { alert("start"); intel.xdk.cache.clearAllCookies(); alert("1"); intel.xdk.cache.clearMediaCache(); alert("2"); intel.xdk.cache.setCookie("thing123","testthing",-1); alert(intel.xdk.cache.getCookie("thing123")); alert("end"); }); &lt;/script&gt; &lt;/head&gt; &lt;body id="afui"&gt; &lt;!-- IMPORTANT: Do not include a weinre script tag as part of your release builds! --&gt; &lt;!-- Place your remote debugging (weinre) script URL from the Test tab here, if it does not work above --&gt; &lt;!-- &lt;script src="http://debug-software.intel.com/target/target-script-min.js#insertabiglongfunkynumberfromthexdkstesttab"&gt;&lt;/script&gt; --&gt; &lt;div id="content" class="uwrap"&gt; &lt;div class="upage vertical-col left panel" id="mainpage" data-header="none" data-footer="none"&gt;&lt;a class="button widget uib_w_1 d-margins" data-uib="app_framework/button" data-ver="1"&gt;Ceci n'est pas une button&lt;/a&gt; &lt;/div&gt; &lt;/div&gt; &lt;/body&gt; &lt;/html&gt;</PRE> <P>When I run this app in debug, "start" is displayed, but "1" is not. I get this error</P> <P>Uncaught TypeError: Cannot read property 'clearAllCookies' of undefined&nbsp;</P> <P>In the plugin settings, I have Cordova Device, Globalization, and Splashscreen, as well as XDK Cache and Device enabled.</P> <P>Help would be very much appreciated.</P> Thu, 12 Mar 2015 04:11:48 GMT https://community.intel.com/t5/Software-Archive/intel-xdk-cache-undefined-Cannot-read-property-clearAllCookies/m-p/1047618#M48614 Daniel_B_3 2015-03-12T04:11:48Z https://community.intel.com/t5/Software-Archive/intel-xdk-cache-undefined-Cannot-read-property-clearAllCookies/m-p/1047619#M48615 <P>intel.xdk.device is also null</P> <P>Truly stumped.</P> <P>&nbsp;</P> <P>Solved. Disabled autolaunch and added this</P> <PRE class="brush:jscript;"> &lt;script type="text/javascript" language="javascript"&gt; document.addEventListener("deviceready", onDeviceReady, false); function onDeviceReady() { setTimeout(function () { $.ui.launch(); }, 50); } &lt;/script&gt;</PRE> <P>&nbsp;</P> Thu, 12 Mar 2015 05:42:00 GMT https://community.intel.com/t5/Software-Archive/intel-xdk-cache-undefined-Cannot-read-property-clearAllCookies/m-p/1047619#M48615 Daniel_B_3 2015-03-12T05:42:00Z https://community.intel.com/t5/Software-Archive/intel-xdk-cache-undefined-Cannot-read-property-clearAllCookies/m-p/1047620#M48616 <P>Based on the index.html file you are showing, I'm betting that the template you used includes an event called "app.Ready" that indicates that all DOM, legacy and Cordova read events have completed. Trigger on that event before you try to access any Cordova or XDK functions, the underlying native system needs to finish initialization before you can call that stuff.</P> <P>If it's the template I'm thinking of, there should be an xdk/init-dev.js file and there might be a js/init-app.js file and js/app.js file. The first generates the app.Ready event. The last two provide examples of how to init your code. Lots of comments in those files.</P> Sat, 14 Mar 2015 00:10:17 GMT https://community.intel.com/t5/Software-Archive/intel-xdk-cache-undefined-Cannot-read-property-clearAllCookies/m-p/1047620#M48616 PaulF_IntelCorp 2015-03-14T00:10:17Z