idevicesyslog managed by appium when not requested

[kazzmir]

The problem

The appium-ios-driver will 1) kill any existing idevicesyslog processes for the given udid being tested (https://github.com/appium/appium-ios-driver/blob/30b3c545278cba286b786c8360812164cf7d5f3e/lib/device-log/ios-log.js#L279) and 2) spawn a new idevicesyslog even if the showIOSLog capability is not set.

Environment

• Appium version (or git revision) that exhibits the issue: 1.8.1
• Desktop OS/version used to run Appium: macos
• Mobile platform/version under test: ios
• Real device or emulator/simulator: real

Details

I run my own idevicesyslog but it is killed by appium when a new session is started. I would prefer that appium does not kill my idevicesyslog process. My current workaround is to copy the idevicesyslog binary to a new name, thus avoiding being targeted by pkill.

[jlipps]

@mykola-mokhnach @imurchie do we need to run idevicesyslog for our own purposes even if log capture is not requested via caps?

[mykola-mokhnach]

Previously it was necessary because we were reading WDA URL from the log, but now it is not the case anymore. I think we could add a separate capability to not start the log listener automatically. However, this will require to change several other places where we assume that the log listener is running.

[jumois]

I started to use deviceconsole

I think we could add a separate capability to not start the log listener automatically.

This would be great. idevicesyslog has high CPU usage compared to deviceconsole.

[KazuCocoa]

appium/appium-xcuitest-driver#878

[KazuCocoa]

skipLogCapture capability can disable crash, system, safari console and safari network logs by appium/appium-xcuitest-driver#878

[lock]

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.