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.

After upgrading to 1.2.2 (from 1.2.1), fail to start iOS device log capture via deviceconsole

See original GitHub issue

After upgrading to 1.2.2 (from 1.2.1), fail to start iOS device log capture via deviceconsole.

info: [debug] Starting iOS device log capture via deviceconsole
error: iOS log capture failed: spawn ENOENT
info: [debug] Cleaning up appium session
error: Failed to start an Appium session, err was: Error: spawn ENOENT
info: [debug] Error: spawn ENOENT
    at errnoException (child_process.js:1000:11)
    at Process.ChildProcess._handle.onexit (child_process.js:791:34)
info: [debug] Responding to client with error: {"status":33,"value":{"message":"A new session could not be created. (Original  error: spawn ENOENT)","code":"ENOENT","errno":"ENOENT","syscall":"spawn","origValue":"spawn ENOENT"},"sessionId":null}
info: <-- POST /wd/hub/session 500 1780.745 ms - 197

After investigating the source code lib/devices/ios/ios-log.js, I find the error was caused by the absence of the executable devicesyslog.

$ cd /usr/local/lib/node_modules/appium/build/deviceconsole/
$ ls -1
Makefile
MobileDevice.framework
MobileDevice.h
deviceconsole.xcodeproj
main.c

So I compile it manually and the issue gets resolved. I think this step (compilation) should be done automatically.

Issue Analytics

  • State:closed
  • Created 9 years ago
  • Comments:45 (9 by maintainers)

github_iconTop GitHub Comments

1reaction
ViniGoyalcommented, Jul 23, 2015

Hi All, I am using appium 1.4.8, I tried all the methods mentioned above, but I cannot see Deviceconsole.xcodeproject in under my deviceconsole folder, there is only one executable file named “deviceconsole”.What should I do?

0reactions
imurchiecommented, May 13, 2016

Please start a new issue with all the information asked. This is too muddied to be able to follow what the actual problem is.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Not able to use Real IOS device through Appium 1.2.2
When I start the script through Eclipse after starting the appium server ( Starting normally ) it throws the error in Appium console...
Read more >
Diagnosing issues using crash reports and device logs
Diagnose problems using device console logs. Apple devices maintain a continuous in-memory transcript of operations in the operating system and individual apps.
Read more >
[Appium][Issue][1.2.2] iOS log capture failed: spawn ENOENT ...
這個問題已經回報#3503 After upgrading to 1.2.2 (from 1.2.1), fail to start iOS device log capture via deviceconsole,應該將compile 的動作在安裝 ...
Read more >
Network – Switch/Router SCSEM
Note: If the system being tested is Cisco IOS 15.0M, then this control is N/A ... Obtain and review device audit logs that...
Read more >
Source - GitHub
iOS (XCUITest) - Fix failing screenshot issue in Xcode 13.3 and iOS 15.4 ... to get the device density on Android 12 by...
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