question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

pid:2641 xctest client exit with code: 65, signal: null

See original GitHub issue

Actually the inspector was working perfectly, but it suddenly stopped working

Environment check:

  macaca-doctor version: 2.0.15


  Node.js checklist:

  node env: /usr/local/opt/node@10/bin/node
  node version: v10.13.0

  iOS checklist:

  Xcode Command Line Tools is ready, version: 2354.
  xcodebuild version: 10.1
  iproxy[usbmuxd] is installed at: `/usr/local/bin/iproxy`
  ios_webkit_debug_proxy is installed at: `/usr/local/bin/ios_webkit_debug_proxy`

  Android checklist:

  JAVA version is `11`
  JAVA_HOME is not set
  ANDROID_HOME is set to `/Users/rafaelcarvalho/Library/Android/sdk`
  Platforms is set to `/Users/rafaelcarvalho/Library/Android/sdk/platforms/android-28`
  ADB tool is set to `/Users/rafaelcarvalho/Library/Android/sdk/platform-tools/adb`
  Not accepted Android SDK license agreements
  Command Line Tools: gradle is uninstalled

  Installed driver list:

  ios: 2.0.35

  • app inspector version / 版本号:
2.0.21
  • os version / 系统:
Mojave 10.14.1 (18B75)
  • device information / 设备版本:
Simulator iphone SE 11.4 (but it doesn not work with any version)
  • terminal log / 终端输出信息:

try app-inspector -u xxxx --verbose for more log detail.

 ✘  ~  app-inspector -u 40B4361A-6FCA-45B9-994C-6E58352CD063 --verbose
>> server.js:16:12 [master] pid:2641 server start with config:
 { port: 5678,
  verbose: true,
  udid: '40B4361A-6FCA-45B9-994C-6E58352CD063',
  ip: '192.168.0.3',
  host: 'MacBook-Rafael.local',
  loaded_time: '2018-11-29 21:13:57' }
>> app-inspector.js:45:12 [master] pid:2641 server start at: http://192.168.0.3:5678
>> xctest-client.js:55:14 [master] pid:2641 project path: /Users/rafaelcarvalho/.npm-global/lib/node_modules/app-inspector/node_modules/xctestwd/XCTestWD/XCTestWD.xcodeproj
>> xctest-client.js:247:14 [master] pid:2641 xcode version: 10.1
>> XCTestWD version: 1.4.5
>> xctest-client.js:195:18 [master] pid:2641 please check project: /Users/rafaelcarvalho/.npm-global/lib/node_modules/app-inspector/node_modules/xctestwd/XCTestWD/XCTestWD.xcodeproj
>> xctest-client.js:195:18 [master] pid:2641 please check project: /Users/rafaelcarvalho/.npm-global/lib/node_modules/app-inspector/node_modules/xctestwd/XCTestWD/XCTestWD.xcodeproj
>> xctest-client.js:195:18 [master] pid:2641 please check project: /Users/rafaelcarvalho/.npm-global/lib/node_modules/app-inspector/node_modules/xctestwd/XCTestWD/XCTestWD.xcodeproj
>> xctest-client.js:286:14 [master] pid:2641 killing runnerProc pid: 2644
>> xctest-client.js:206:16 [master] pid:2641 xctest client exit with code: 65, signal: null

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:6 (2 by maintainers)

github_iconTop GitHub Comments

1reaction
jade685commented, Mar 12, 2019

@SirCYong This is how I solve the problem.

step1 : recompile your XCTestWD.xcodeproj in xcode, make sure it’s signed. step2 : check if there’s an app called XCTestWDUITests installed on your device. If not, go to /usr/local/lib/node_modules/app-inspector/node_modules/xctestwd/XCTestWD on your terminal. You might not have same path as mine, just find where XCTestWD is. Then compile XCTestWD.xcodeproj ( command : xcodebuild -project XCTestWD.xcodeproj -scheme XCTestWDUITests -destination 'id=DEVICE-ID' test)

Then try restart app inspector, it should be working.

0reactions
SirCYongcommented, Mar 12, 2019

I also encountered the same problem, how can I solve it?

Read more comments on GitHub >

github_iconTop Results From Across the Web

xcodebuild exited with code '65' and signal 'null' - Stack Overflow
Hello I am having issues in launching ios real device for testing. My xcode version: 11.2.1 (11B500) Appium Version : 1.13.0 (1.13.0.20190505.6).
Read more >
Xcodebuild exited with code '65' and signal 'null' - Issues/Bugs
I have gone through multiple links but could not find a single possible solution. I am trying to run appium 1.7.2 iOS version...
Read more >
Encounter xcodebuild exited with code '65' and signal 'null'
Your .ipa application and/or WebDriverAgent is not signed correctly.Sign and rebuild the WebDriverAgent XCode project with your developer certificate.
Read more >
Appium XCUITest Driver Real Device Setup
... by info XCUITest xcodebuild exited with code '65' and signal 'null' . This usually means that the necessary code signing is not...
Read more >
xcodebuild Exit Code 65 - CircleCI
The best way to mitigate this is to boot the iOS Simulator early with the help of the instrument's command line tool. This...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found