So, there's a list of things you can try w/weinre issues. - is the weinre server on your whitelist (for Cordova) - try turning using --verbose and --debug when you invoke weinre, and see if anything appears in the terminal where you run weinre - try running the demo apps provided with weinre (link available on your weinre server's "home page"
On Fri, Jan 10, 2014 at 1:52 PM, Jonathan Silverman (JIRA) <[email protected]>wrote: > > [ > https://issues.apache.org/jira/browse/CB-5759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13868120#comment-13868120] > > Jonathan Silverman commented on CB-5759: > ---------------------------------------- > > Update: Removing "use strict" didn't fix the combo of Wenre and xhr.js. > > I am working on getting the developer license but its a slow process since > I need authorization. > > Haven't found a way to get my self-signed certificates trusted in > XDK/node-webkit. Even though I trusted them in Safari like you're supposed > to. > > Basically means that both Ripple+ChromeDevTools and Weinre are useless to > me right now, and for different reasons. > > Ripple's useless to me right now because it won't connect to any of my > self-signed https:// endpoints. If trust is really the issue, I just need > to get my certs into the trust store. > > Weinre because it doesn't work with xhr.js and I don't want to use Intel's > getRemoteDataExt function. > > > Conflict between xhr.js from Intel XDK and Weinre remote hook script > > -------------------------------------------------------------------- > > > > Key: CB-5759 > > URL: https://issues.apache.org/jira/browse/CB-5759 > > Project: Apache Cordova > > Issue Type: Bug > > Components: weinre > > Affects Versions: 2.9.0 > > Environment: OS X, Windows > > Reporter: Jonathan Silverman > > Assignee: Patrick Mueller > > Priority: Critical > > Labels: javascript > > > > I have code that proves a conflict between xhr.js and weinre. > > Cross-post from: > https://www.html5dev-software.intel.com/viewtopic.php?f=34&t=5024 > > Adding xhr.js causes Weinre to not work, as no connectable targets > appear. http://cl.ly/image/1L0l060e381G > > I can confirm that xhr.js and Weinre conflict. If they are both added, > neither work. If one is added, and not the other, it works. > > Example: > > {code} > > <script src="intelxdk.js"></script> > > <script src="xhr.js"></script> > > <script type="text/javascript"> > > /* This code is used to run as soon as Intel activates */ > > var onDeviceReady=function(){ > > //hide splash screen > > intel.xdk.device.hideSplashScreen(); > > > > $.get("https://dev-1-web-geo.meteostar.local";).done(function(data){ > alert(data); }); > > }; > > > document.addEventListener("intel.xdk.device.ready",onDeviceReady,false); > > </script> > > {code} > > Works > > {code} > > <script src="intelxdk.js"></script> > > <script src=" > http://debug-software.intel.com/target/target-script-min.js#QhYeZC6N-jY-XBnNnuS5DqN6Ti72PEzRd1Oeu_TKT9g > "></script> > > <script src="xhr.js"></script> > > <script type="text/javascript"> > > /* This code is used to run as soon as Intel activates */ > > var onDeviceReady=function(){ > > //hide splash screen > > intel.xdk.device.hideSplashScreen(); > > > > $.get("https://dev-1-web-geo.meteostar.local";).done(function(data){ > alert(data); }); > > }; > > > document.addEventListener("intel.xdk.device.ready",onDeviceReady,false); > > </script> > > {code} > > Doesn't > > It doesn't seem to matter where you put the Weinre script. No matter > what, it breaks xhr.js. It broke when included both before and after the > xhr.js include. > > To me, this is critical because I would like to use Weinre to debug and > test while using xhr.js to enable cross-origin XHRs to the app. > > This seems to affect Weinre 2.0.0-pre-HHOSN197, if that's the correct > version number. > > > > -- > This message was sent by Atlassian JIRA > (v6.1.5#6160) > -- Patrick Mueller http://muellerware.org
