"install failed - missing shared library" err not caught

[jwallis]

I'm not sure how much control appium has over adb and its return codes, but my test run failed with

2013-11-21 12:51:37,720 [DEBUG] mats.exec_logger.AppiumServer:error: Activity used to start app doesn't exist! Make sure it exists [service.py:47]

when the root cause was the previously run command:

2013-11-21T18:51:35.391Z - debug: executing: "/.../platform-tools/adb" -s emulator-5554 shell pm install -r /data/local/tmp/97f063dd63f1909a776e729aabc930ce.apk

which threw no error as far as I saw.  The uncaught or unreported error I found when I tried the adb cmd on the cmd line was:

$ "/.../platform-tools/adb" -s emulator-5554 shell pm install -r /data/local/tmp/97f063dd63f1909a776e729aabc930ce.apk

pkg: /data/local/tmp/97f063dd63f1909a776e729aabc930ce.apk

Failure [INSTALL_FAILED_MISSING_SHARED_LIBRARY]

So it was pretty easy to see what happened, but it would be a nice to have if appium caught any adb error and raised it.

I just realized maybe this is not the place for such a request...

[Sai Manoj Bandi]

What you are mentioning here may not be the problem.

This line tells the problem.

" Activity used to start app doesn't exist! Make sure it exists"

This means that you didn't mention the main activity(The activity used to start the app) properly...
Try changing the activity name.

[jwallis]

That is a very good idea, I did have problems with that (figuring out the correct package name) when I first started, and I think a lot of people have that problem, but I am sure I have the right package name.  I know this because after updating my AVD to have the correct shared libraries, my problem went away.  It was definitely not able to install due to missing those libraries at first, then that's why the app did not exist when it tried to start the activity.  Thank you for your response though, I know that's a common problem...