It sounds like you're just using the Chrome Inspector and not our remote inspection feature. To start using remote inspection, open the Edge Inspect Chrome extension dialog that contains your list of devices and click on the <> icon next to the device you want to inspect. A new browser window should open up and you should see be able to see the DOM and console logs from your device there. You may need to click on the link to your device in the first page of that window.
FYI, a number of the tabs will be empty due to limitations of the tool we're using to do remote inspection (weinre), but you definitely should be able to see and modify the DOM on your device. The modifications will only affect the selected device, not all your devices or your computer.
Hope this helps, let me know if you have any more questions,
Yes that was the problem, thanks!
I've got similar problem so posting it here.
I'm using Edge Inspect with iPhone 3GS and New iPad, I can browse pages just fine - I navigate in Chrome and see it duplicated on devices.
But when I click <> link and see the debugger open, it loads for some time and shows me an empty page, with title "weinre: target not connected".
What can be the issue?
PS: running chrome in windows 7
Can you post a full screen capture of the window you're seeing?
That's very odd. It looks like weinre is somehow being partially blocked. We're puzzled.
- Are you on a corporate or personal network? If you're on a personal network, you might try turning off any software or firewall hardware you have running and see if that makes a difference.
- Try going to this URL in the browser on your computer and on your device: http://debug.edgeinspect.adobe.com/ Do you see a splash page that says "Edge Inspect powered by weinre" on each?
- Does it make a difference if you test a different page? Give http://google.com a try and see if you get a different-looking weinre window.
- Try taking Edge Inspect out of the loop and see if that changes anything...
- Put this script tag into your web page: <script src="http://debug.edgeinspect.adobe.com/target/target-script-min.js#whoisthatme"></script>
- Reload the page in Chrome.
- In a new browser tab/window go to http://debug.edgeinspect.adobe.com/client/#whoisthatme
- Does that get you a working weinre window?
- If so, load the page on your device and on your computer refresh the /client#whoisthatme window
- Does that work? (NOTE: you can use any identifier after the hash as long as it's the same in both your script tag and the URL you input)
Let me know what happens when you do all that and we'll figure out how to proceed,
Just as a data point; I have not tried your above steps but for me -- it worked fine in Chrome 26, but fails in any version of Chrome v28 with the following console log:
1. Not a issue; chrome v26 works, chrome 28 doesn't.
2. Interesting enough the Edge Inspect seems to ignore sending http://debug.edgeinspect.adobe.com to the phone. The phone always maintains the last url it was at. (i.e. if I navigate to google.com, then google.com stays on the phone, and the debug site shows up in my chrome 28 browsers) -- doing a refresh on either device still leaves the phone (& refreshes that url) at the last url before the debug site.
3. Get the same console log (on my machine) as I posted earlier when trying to "inspect"
4. Not tried as I think my error I reported earlier is the issue. But if you really need me to try this I can setup a dummy page somewhere with this in it.
- I'm on Chrome 26 with auto-updating. If you've got Chrome 28 you must be downloading beta versions of Chrome, right? This sounds like a Chrome issue rather than an Edge Inspect issue.
- Correct. By design there are certain URLs we don't send to the devices. debug.edgeinspect.adobe.com is one, file:/// URLs are another example since the device couldn't reach them anyway.
3 & 4. Like I said, I think this is a Chrome issue with the alpha/beta version you have. Have you seen any similar bug reports? You might try looking for error reports about weinre not working with that version of Chrome.
Well, guess we could/should have looked on the Weinre newgroup first -- this appears to be a KNOWN issue with weinre and Chrome v28.
The bug tracker seems to be down so I can't see if this has been fixed in the later code since it was reported...
1 person found this helpful
Yeah, apparently I was on the Dev channel which is also now using v28. You can uninstall chrome, and re-install to downgrade to the stable change v26. However v28 is coming soon. It isn't very long after it is on the Dev channel before it is released to the stable channel.
Accordig to the newsgroup post v28 supports a new html5 CSS property which conflicts with the weinre code... So it is actually a weinre issue; which Edge is using as its base.
Also, checking the Weinre changelog: http://people.apache.org/~pmuellr/weinre/docs/latest/ChangeLog.html Appears that they might have fixed it in the "unreleased" version. You might need to get one of your devs to go and grab the fixes from the git repositories and fix your copy. :-)
1 person found this helpful
One more thing -- for those who are using Chrome 27 or 28 and don't want to downgrade. Adobe was nice enough to allow us to use our own weinre server. So you can easily run your own weinre server (took me about 5 minutes); which you must get the current "unofficial" build from:
http://people.apache.org/~pmuellr/weinre/ as it has the fixes in it..
Then right mouse click in Chrome on the Edge extension and click settings, then set Edge to use your own server...
Works really well and is really FAST!!!
Wow, thanks for the follow-ups Nathanael!
We'll see about grabbing that patch and applying it to our hosted version of weinre
FYI, we are working on updating our version of weinre now. We hope to have a version that works with Chrome 28 posted in the next couple of hours.
For everyone using Chrome 27 or above - we've integrated the weinre fixes and pushed those changes live to our server. Let us know if you see any problems.