ios-webkit-debug-proxy-launcher.js requires an iOS 10 device to manually open Safari before connecting to it

The problem

iOS Webkit Debug Proxy will not connect to my iOS 10 device when launching the proxy through Appium’s supplied ios-webkit-debug-proxy-launcher.js. Executing node ios-webkit-debug-proxy-launcher.js -c <UDID>:27753 -d outputs RUNNING: ios_webkit_debug_proxy -c <UDID>:27753 -d and there is no more output after that. Once I manually open Safari on my device, then the usual output that shows a device is connected will be appended to stdout. If I run the proxy directly without this Javascript file, e.g. ios_webkit_debug_proxy -c <UDID>:27753 -d, it works fine. If I connect an iOS 9 device and run the proxy the same way as before using the Javascript file, it works fine.

Environment

• Appium version (or git revision) that exhibits the issue: 1.6.0
• Last Appium version that did not exhibit the issue (if applicable):
• Desktop OS/version used to run Appium: Mac 10.11.6
• Node.js version (unless using Appium.app|exe): 6.9.1
• Mobile platform/version under test: iOS 10.0.2
• Real device or emulator/simulator: Real device
• Appium CLI or Appium.app|exe: Appium CLI

Details

I am on a work computer and am locked out of /usr/bin/env. Therefore, I need to explicitly specify the node command when running the Javascript file. I am not certain what effect this has, if any. I’ve tried removing the shebang line specifying to use node at the top of ios-webkit-debug-proxy-launcher.js but that did not help.

Link to Appium logs

Part of the problem is I’m not receiving any logs.

Code To Reproduce Issue [ Good To Have ]

node ios-webkit-debug-proxy-launcher.js -c <UDID>:27753 -d

[imurchie]

The issue with running node main.js is that the file you want to run is the transpiled version, which is build/lib/main.js.

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.