How to setup appium for testing on Android 2.3.5 device

Hi

I’m new to Appium. Using Java and TestNG to write my test cases.
Appium version: v1.2.2 (REV cf6ff5939ddc6b4d45fcbabfbfe13c950e0058c4)
I’m running on a MAC OS X 10.9.4
I can run on a Android 4.4.4 device (with slightly different capabilities defined). I have started the Appium server manually.

I would like to have my already written test to run on a Android 2.3.5 device (Samsung Galaxy S II). But get an exception when instantiating the AppiumDriver.

I’m doing the following in my code:

DesiredCapabilities capabilities = new DesiredCapabilities();
capabilities.setCapability("app", cfg.getAppPath());
capabilities.setCapability("platformName", "Android");
capabilities.setCapability("deviceName", "Selendroid");
capabilities.setCapability("automationName", "Selendroid");
capabilities.setCapability("appPackage", "com.some.package");
capabilities.setCapability("appActivity", "SomeActivity");
return new AppiumDriver(new URL("http://127.0.0.1:4723/wd/hub"), capabilities);

And I get the following error message:
2014-09-16 10:12:50.217 ERROR org.openqa.selenium.SessionNotCreatedException: A new session could not be created. (Original error: Could not find aapt; do you have the Android SDK installed and the tools + platform-tools folders added to your PATH?) (WARNING: The server did not provide any stacktrace information)

I have this in my PATH
/Users/ffsocial/Android/sdk/build-tools:/Users/ffsocial/Android/sdk/platform-tools:/Users/ffsocial/Android/sdk/tools:/Users/ffsocial/Android/sdk

Where is the “aapt” file suppose to be located?

I serrched for it and found these locations:
find /Users/ffsocial -name aapt
/Users/ffsocial/.Trash/adt-bundle-mac-x86_64-20140702/sdk/build-tools/android-4.4W/aapt
/Users/ffsocial/Android/adt-bundle-mac-x86_64-20140702/sdk/build-tools/android-4.4W/aapt
/Users/ffsocial/Android/sdk/build-tools/17.0.0/aapt
/Users/ffsocial/Android/sdk/build-tools/18.0.1/aapt
/Users/ffsocial/Android/sdk/build-tools/18.1.0/aapt
/Users/ffsocial/Android/sdk/build-tools/18.1.1/aapt
/Users/ffsocial/Android/sdk/build-tools/19.0.0/aapt
/Users/ffsocial/Android/sdk/build-tools/19.0.1/aapt
/Users/ffsocial/Android/sdk/build-tools/19.0.2/aapt
/Users/ffsocial/Android/sdk/build-tools/19.0.3/aapt
/Users/ffsocial/Android/sdk/build-tools/19.1.0/aapt
/Users/ffsocial/Android/sdk/build-tools/20.0.0/aapt
/Users/ffsocial/Android/sdk_old/build-tools/17.0.0/aapt
/Users/ffsocial/Android/sdk_old/build-tools/18.0.1/aapt
/Users/ffsocial/Android/sdk_old/build-tools/18.1.0/aapt
/Users/ffsocial/Android/sdk_old/build-tools/18.1.1/aapt
/Users/ffsocial/Android/sdk_old/build-tools/19.0.0/aapt
/Users/ffsocial/Android/sdk_old/build-tools/19.0.1/aapt
/Users/ffsocial/Android/sdk_old/build-tools/19.0.2/aapt
/Users/ffsocial/Android/sdk_old/build-tools/android-4.4.2/aapt
/Users/ffsocial/Android/sdk_old/platforms/android-3/tools/aapt
/Users/ffsocial/Android/sdk_old/platforms/android-4/tools/aapt

Have I missed anything in my installation? Please help.

Regards,
Alex

For temporary workaround you can put the sdk path in the appium tool