Support Center

Name is required.
Email address is required.
Invalid email address
Answer is required.
Exceeding max length of 5KB

Calabash IOS not running on test cloud

Rogério Peixoto Mar 29, 2016 03:52PM CEST

Hello, I'm trying to run a calabash ios project on the test cloud but I've been unsuccessful. The same code runs fine locally in the simulator.

Here is some problems I've found on the Calabash log:

2016-03-24 06:43:17 -0700 [RunLoop:debug]: xcrun instruments -w 14b6d6847ef701c1bb8152bbad30346670479c99 -D /Users/testdroid/.run-loop/results/2016-03-24_06-43-16/trace -t Automation raizen.Acelera -e UIARESULTSPATH /Users/testdroid/.run-loop/results/2016-03-24_06-43-16 -e UIASCRIPT /Users/testdroid/.run-loop/results/2016-03-24_06-43-16/_run_loop.js >& /Users/testdroid/.run-loop/results/2016-03-24_06-43-16/run_loop.out
2016-03-24 06:43:17 -0700 [RunLoop:debug]: Preparation took 2.462019 seconds
2016-03-24 06:43:47 -0700 [RunLoop:debug]: Error while writing to fifo. RunLoop::Fifo::NoReaderConfiguredError
2016-03-24 06:43:47 -0700 [RunLoop:debug]: Failed to launch. Error while writing to fifo. RunLoop::Fifo::NoReaderConfiguredError: Error while writing to fifo. RunLoop::Fifo::NoReaderConfiguredError
Unable to start. Make sure you've set APP_BUNDLE_PATH to a build supported by this simulator version

"Timed out waiting for UIAutomation run-loop Error while writing to fifo. RunLoop::Fifo::NoReaderConfiguredError.

Logfile: /Users/testdroid/.run-loop/results/2016-03-24_06-43-16/run_loop.out

2016-03-24 06:43:19.697 instruments[3204:10032] WebKit Threading Violation - initial use of WebKit from a secondary thread.

/Users/testdroid/.rbenv/versions/2.1.1/lib/ruby/gems/2.1.0/gems/calabash-cucumber-0.17.1/lib/calabash-cucumber/launcher.rb:729:in `new_run_loop'
/Users/testdroid/.rbenv/versions/2.1.1/lib/ruby/gems/2.1.0/gems/calabash-cucumber-0.17.1/lib/calabash-cucumber/launcher.rb:584:in `relaunch'
/Volumes/VMware Shared Folders/test/features/support/01_launch.rb:43:in `Before'

Up 0 rated Down
Lukasz Mar 30, 2016 11:52AM CEST Bitbar Testing help Agent

You can be interested in reading but the last time we came across similar exception it was because tested app have triggered notification which was in front of tested app to investigate it more the best if You will send email to with direct link to test-run.

BR, Lukasz

Post Your Public Answer

Your name (required)
Your email address (required)
Answer (required)

Contact Us
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
Invalid characters found