Closed Bug 1333527 Opened 8 years ago Closed 7 years ago

Valence not working for Safari on iOS 10 devices.

Categories

(DevTools :: about:debugging, defect, P3)

54 Branch
x86_64
macOS
defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: joseramonrivera21, Unassigned)

References

(Blocks 1 open bug)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:54.0) Gecko/20100101 Firefox/54.0 Build ID: 20170124195206 Steps to reproduce: 1. Plug an iOS 10+ device via USB. 2. Make sure Web Inspector is enabled on the device's Safari settings. 3. Open any page with Safari in the device 3. Open WebIDE 4. Select Safari, Firefox and other WebViews on iOS Actual results: I get the following on the Browser Console: valence:ios_webkit_debug_proxy: Could not connect to lockdownd. Exiting.: Permission denied ios-proxy.js:137 valence:ios_webkit_debug_proxy: Unable to attach 8a77caec89aeaa72cdc7e4714aae36233e309334 inspector ios-proxy.js:137 Operation failed: Connecting to Safari, Firefox, and other WebViews on iOS: Error: No iOS device found webide.js:353:5 Error: No iOS device found Stack trace: iOSProxy.start<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://fxdevtools-adapters-at-mozilla-dot-org/lib/util/ios-proxy.js:100:13 Expected results: the iOS Device should be connected and one should be able to debug it.
OS: Unspecified → Mac OS X
Hardware: Unspecified → x86_64
Component: Untriaged → Developer Tools: WebIDE
This is a known issue. See https://github.com/mozilla/valence/issues/222 and similar issues in that repo.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P2
Blocks: dbg-remote
Component: Developer Tools: WebIDE → Developer Tools: about:debugging
Priority: P2 → P3
Summary: WebIDE not working for Safari on iOS 10 devices. → Valence not working for Safari on iOS 10 devices.
Valence is no longer supported.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.