Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to run spoon with multiple devices attached (OSX) #177

Closed
TealOcean opened this issue Mar 7, 2014 · 14 comments
Closed

Unable to run spoon with multiple devices attached (OSX) #177

TealOcean opened this issue Mar 7, 2014 · 14 comments

Comments

@TealOcean
Copy link

So I'm getting this error when I attach more than 1 device and run spoon with this plugin:

STDERR Error: Could not find or load main class com.squareup.spoon.SpoonDeviceRunner

My setup is:
OSX 10.9 Mavericks
Spoon 1.1.1
Robotium 5.0.1

This only occurs with more than 1 device attached.

@TealOcean
Copy link
Author

Here's the output when I use debug mode:

2014-03-07 12:44:00 [SR.runTests] Executing instrumentation suite on 2 device(s).
2014-03-07 12:44:00 [SR.runTests] Application: com.nfl.now.dev from /Users/tealocean/Development/NFLNow/NFLNow/build/apk/NFLNow-dev-debug-unaligned.apk
2014-03-07 12:44:00 [SR.runTests] Instrumentation: com.nfl.now.dev.test from /Users/tealocean/Development/NFLNow/NFLNow/build/apk/NFLNow-dev-debug-test-unaligned.apk
2014-03-07 12:44:00 [SR.runTests] [2de8ba9f] Starting execution.
2014-03-07 12:44:00 [SR.runTests] [059f3c01] Starting execution.
2014-03-07 12:44:00 [SDR.runInNewProcess] [2de8ba9f]
2014-03-07 12:44:00 [SDR.runInNewProcess] [059f3c01]
2014-03-07 12:44:00 [SDR.printStream] [2de8ba9f] STDERR Error: Could not find or load main class com.squareup.spoon.SpoonDeviceRunner
2014-03-07 12:44:00 [SDR.printStream] [059f3c01] STDERR Error: Could not find or load main class com.squareup.spoon.SpoonDeviceRunner
2014-03-07 12:44:00 [SDR.runInNewProcess] Process.waitFor() finished for [2de8ba9f] with exitCode 1
2014-03-07 12:44:00 [SDR.runInNewProcess] Process.waitFor() finished for [059f3c01] with exitCode 1
2014-03-07 12:44:00 [SR$1.run] [059f3c01] Execution done. (0 remaining [])
2014-03-07 12:44:00 [SR$1.run] [2de8ba9f] Execution done. (0 remaining [])

@TealOcean
Copy link
Author

Here's the output if I have one device attached:

2014-03-07 12:46:44 [SR.runTests] Executing instrumentation suite on 1 device(s).
2014-03-07 12:46:44 [SR.runTests] Application: com.nfl.now.dev from /Users/tealocean/Development/NFLNow/NFLNow/build/apk/NFLNow-dev-debug-unaligned.apk
2014-03-07 12:46:44 [SR.runTests] Instrumentation: com.nfl.now.dev.test from /Users/tealocean/Development/NFLNow/NFLNow/build/apk/NFLNow-dev-debug-test-unaligned.apk
2014-03-07 12:46:44 [SR.runTests] [2de8ba9f] Starting execution.
2014-03-07 12:46:44 [SDR.run] InstrumentationInfo: [com.squareup.spoon.SpoonInstrumentationInfo@1b3d0353[applicationPackage=com.nfl.now.dev,instrumentationPackage=com.nfl.now.dev.test,testRunnerClass=android.test.InstrumentationTestRunner]]
2014-03-07 12:46:44 [SDR.run] Got realDevice for [2de8ba9f]
2014-03-07 12:46:44 [SDR.run] [2de8ba9f] setDeviceDetails com.squareup.spoon.DeviceDetails@19912a48[model=SM-N9005,manufacturer=samsung,version=4.3,apiLevel=18,language=en,region=GB,isEmulator=false,avdName=<null>]
12:46:44 D/NFLNow-dev-debug-unaligned.apk: Uploading NFLNow-dev-debug-unaligned.apk onto device '2de8ba9f'
12:46:44 D/Device: Uploading file onto device '2de8ba9f'
12:46:50 D/NFLNow-dev-debug-test-unaligned.apk: Uploading NFLNow-dev-debug-test-unaligned.apk onto device '2de8ba9f'
12:46:50 D/Device: Uploading file onto device '2de8ba9f'
2014-03-07 12:46:54 [SDR.run] About to actually run tests for [2de8ba9f]

@TealOcean
Copy link
Author

Nevermind figured it out!

@luckyhandler
Copy link

I have the same problem, how did you fix it?

@luckyhandler
Copy link

I still have the problem. Any ideas?

@FisherKK
Copy link

Hello, I have encountered the same problem after 1.5.0 gradle and 1.2.1 runner update. It worked before. Did you manage to fix it by chance?

@trevjonez
Copy link

I have the same symptoms.

Android gradle 1.5.0
spoon 1.2.1

Is there anyway to see exactly what adb commands are being ran by spoon?

@free5ty1e
Copy link

"Nevermind figured it out!"

-Least useful comment to date. This one is more useful than that one.

How did you fix this?!?

@JakeWharton
Copy link
Member

Not as bad as "+1" though. We need a comment uselessness-o-meter.

On Wed, Dec 16, 2015, 5:01 PM free5ty1e notifications@github.com wrote:

"Nevermind figured it out!"

-Least useful comment to date. This one is more useful than that one.

How did you fix this?!?


Reply to this email directly or view it on GitHub
#177 (comment).

@romainpiel
Copy link

Damn I'm stuck on that one too, would you mind explaining how you fixed it @TealOcean ?

@free5ty1e
Copy link

https://xkcd.com/979/

@pr1ntf
Copy link

pr1ntf commented Jan 7, 2016

+1

@Kritarie
Copy link

Kritarie commented Mar 2, 2016

If anyone is still running into this, I was able to fix it by switching to this gradle plugin https://github.com/stanfy/spoon-gradle-plugin from this plugin https://github.com/x2on/gradle-spoon-plugin

@rafaelaazevedo
Copy link

@Kritarie Thanks for this 👍 It's working now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants