=
from：http://www.cnblogs.com/appstest/p/5253257.html
The default 60 seconds seems to be OK, but the timeout is generally a program problem. But in the debugging phase, 60 is not good, because you need to debug elements, but you should wait for a long time.
=
When writing the Appium test code a few days ago, a test case was executed after waiting for a period of time during the execution process. It was found that the following records appeared in the log:
info: [debug] Didn't get a new command in 60 secs, shutting down...
The execution cannot continue because the sessions are closed.
Check the relevant documents because:
Appium's default command interval is 60s. If it is not found within 60s, it will automatically exit.
Solution:
newCommandTimeoutA larger value can be used .
capabilities.setCapability("newCommandTimeout",240);
See the official documentation for more parameters:
http://appium.io/slate/en/master/?ruby#the---default-capabilities-flag
=
=
=