I'm trying to run an small initial set of calabash-android tests on a Samsung Galaxy S3 connected to a Windows 7 laptop and keep getting an "App did not start (RuntimeError)" when trying to start the test server.
I've got Ruby v1.9.3p448, RubyDevKit 4.5.2 (32-bit), Ant 1.9.2, and AnsiCon installed. I've installed calabash-android 0.4.20 and all its dependent gems by typing "gem install calabash-android" at the command prompt. I've created a signed APK using Xamarin Studio and the release keystore. My initial feature set of six steps is parsed correctly when run with the --dry-run flag.
When I type "calabash-android run com.XYZ.ABC.apk --verbose the following things happen:
At this point we get the "App did not start (RuntimeError)" message. Here's the appropriate detail from the command line.
2014-03-11 08:10:05 - Starting test server using:
2014-03-11 08:10:05 - "C:\Users\BMaya\AppData\Local\Android\android-sdk/platform-tools/adb.exe" -s 4df18df165d46f4d shell am instrument -e target_package com.trimble.terraflex -e main_activity trimble.tfm.fieldapp.SplashActivity -e test_server_port 7102 -e debug false -e class sh.calaba.instrumentationbackend.InstrumentationBackend com.trimble.terraflex.test/sh.calaba.instrumentationbackend.CalabashInstrumentationTestRunner
App did not start (RuntimeError)
C:/Ruby193/lib/ruby/gems/1.9.1/gems/calabash-android-0.4.20/lib/calabash-android/operations.rb:505:in `block in start_test_server_in_background'
C:/Ruby193/lib/ruby/gems/1.9.1/gems/retriable-1.3.3.1/lib/retriable/retriable.rb:31:in `perform'
C:/Ruby193/lib/ruby/gems/1.9.1/gems/retriable-1.3.3.1/lib/retriable/retriable.rb:53:in `retriable'
C:/Ruby193/lib/ruby/gems/1.9.1/gems/calabash-android-0.4.20/lib/calabash-android/operations.rb:504:in `start_test_server_in_background'
C:/Ruby193/lib/ruby/gems/1.9.1/gems/calabash-android-0.4.20/lib/calabash-android/operations.rb:93:in `start_test_server_in_background'
I've also tried running the tests from the Ruby command prompt with the same results:
I've googled around and tried the following things:
Any help is appreciated. Let me know if you need more info.
Thanks in advance.
I was facing the same issue. After days of looking for a solution, I found that the proxies on my machine was causing the issue. Check if you have proxies set on your machine. Go to Terminal if you are on Mac and execute the below statement to unset the proxies export http_proxy=""
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With