search

zzwendy / robotium

Automatically exported from code.google.com/p/robotium
0 stars 0 forks source link

Robotium Recorder failing to launch app on mobile device #662

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
I was able to successfully run the ExampleTestProject_Eclipse_v5.3.zip sample 
app from the Robotium tutorial. When I attempt to use Robotium Recorder with my 
own app APK, it installs the re-signed APK file to my device but then fails to 
launch the app and throws an IncompatibleClassChangeError. 

The following output is logged to console (note- app name changed to cover my 
ass) 

[2015-02-24 12:00:24 - MyAppExecutor] ------------------------------
[2015-02-24 12:00:24 - MyAppExecutor] Android Launch!
[2015-02-24 12:00:24 - MyAppExecutor] adb is running normally.
[2015-02-24 12:00:24 - MyAppExecutor] Performing 
android.test.InstrumentationTestRunner JUnit launch
[2015-02-24 12:00:24 - MyAppExecutor] Automatic Target Mode: using device 
'FA44GWM06469'
[2015-02-24 12:00:24 - MyAppExecutor] Uploading MyAppExecutor.apk onto device 
'FA44GWM06469'
[2015-02-24 12:00:24 - MyAppExecutor] Installing MyAppExecutor.apk...
[2015-02-24 12:00:25 - MyAppExecutor] Success!
[2015-02-24 12:00:25 - MyAppExecutor] Launching instrumentation 
android.test.InstrumentationTestRunner on FA44GWM06469
[2015-02-24 12:00:34 - MyAppExecutor] Test run failed: Instrumentation run 
failed due to 'java.lang.IncompatibleClassChangeError'

Can you suggest any steps to fix this issue?

Original issue reported on code.google.com by blaze...@gmail.com on 24 Feb 2015 at 5:07

GoogleCodeExporter commented 9 years ago 
Thanks for reporting this. Would it be possible for you to send us the APK? 
Email address: support@robotium.com

Original comment by renasr...@gmail.com on 24 Feb 2015 at 7:24

GoogleCodeExporter commented 9 years ago 
Hello,

I am sending over the APK in response to the issue I opened:
https://code.google.com/p/robotium/issues/detail?id=662

Original comment by blaze...@gmail.com on 24 Feb 2015 at 7:36

GoogleCodeExporter commented 9 years ago 
This seems to be caused by a lib that you're using in your app. Unfortunately 
there is nothing we can do on our end.

Original comment by renasr...@gmail.com on 11 Mar 2015 at 3:02