Appium+Selendroid show error even after giving autmationName

625 visualizzazioni
Passa al primo messaggio da leggere

Abdul Nazer

da leggere,
2 set 2014, 05:49:0802/09/14
a appium-...@googlegroups.com

 Hi

I'm getting following error on attempting to run appium using selendroid on API Level <16, (ie OS 4.1.2)

org.openqa.selenium.SessionNotCreatedException: A new session could not be created. (Original error: Required platform doesn't exist (API level >= 17)) (WARNING: The server did not provide any stacktrace information)


I have set automationName to "Selendroid" as

        capabilities.setCapability("automationName", "Selendroid"); 

My Entire Related Code

DesiredCapabilities capabilities = new DesiredCapabilities();

        

        capabilities.setCapability("deviceName", "Galaxy S2");

        capabilities.setCapability("automationName", "Selendroid"); 

        capabilities.setCapability("platformName", "Android");

        capabilities.setCapability(CapabilityType.BROWSER_NAME"");

        capabilities.setCapability(CapabilityType.VERSION, "4.2");

        capabilities.setCapability(CapabilityType.PLATFORM, "MAC");

        capabilities.setCapability("app", app.getAbsolutePath());

        capabilities.setCapability("app-package","com.******.android");  //For API Level>17

       capabilities.setCapability("app-activity", "com.******.android.activities.*******Activity");  //my case RootActivity

      driver = new RemoteWebDriver(new URL("http://127.0.0.1:4723/wd/hub"), capabilities);

        

   Anyone plz help to get this sorted out?

Isaac Murchie

da leggere,
2 set 2014, 05:59:4802/09/14
a Abdul Nazer, appium-...@googlegroups.com
What version of Appium are you using? Can you provide the server logs?


--
http://appium.io
---
You received this message because you are subscribed to the Google Groups "Appium-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to appium-discus...@googlegroups.com.
Visit this group at http://groups.google.com/group/appium-discuss.
For more options, visit https://groups.google.com/d/optout.

Abdul Nazer

da leggere,
2 set 2014, 06:03:3002/09/14
a Isaac Murchie, appium-...@googlegroups.com
Thanks for quick Reply

My version is : 1.2.1


[TestNG] Running:

  /private/var/folders/hh/mjrld8g12h738zh0lchcgztr0000gp/T/testng-eclipse-430533132/testng-customsuite.xml


FAILED CONFIGURATION: @BeforeMethod setUp

org.openqa.selenium.SessionNotCreatedException: A new session could not be created. (Original error: The following desired capabilities are required, but were not provided: deviceName) (WARNING: The server did not provide any stacktrace information)

Command duration or timeout: 190 milliseconds

Build info: version: '2.42.2', revision: '6a6995d', time: '2014-06-03 17:42:30'

System info: host: 'qbadmins-iMac-163.local', ip: '10.3.0.87', os.name: 'Mac OS X', os.arch: 'x86_64', os.version: '10.9.4', java.version: '1.7.0_60'

Driver info: org.openqa.selenium.remote.RemoteWebDriver

at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)

at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)

at java.lang.reflect.Constructor.newInstance(Constructor.java:526)

at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:204)

at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:156)

at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:599)

at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:240)

at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:126)

at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:153)

at naz.appium.test.AppiumTest.setUp(AppiumTest.java:55)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:606)

at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84)

at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:564)

at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:213)

at org.testng.internal.Invoker.invokeMethod(Invoker.java:653)

at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901)

at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231)

at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)

at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)

at org.testng.TestRunner.privateRun(TestRunner.java:767)

at org.testng.TestRunner.run(TestRunner.java:617)

at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)

at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)

at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)

at org.testng.SuiteRunner.run(SuiteRunner.java:240)

at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)

at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)

at org.testng.TestNG.runSuitesSequentially(TestNG.java:1224)

at org.testng.TestNG.runSuitesLocally(TestNG.java:1149)

at org.testng.TestNG.run(TestNG.java:1057)

at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:111)

at org.testng.remote.RemoteTestNG.initAndRun(RemoteTestNG.java:204)

at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:175)


--
Thanks and Regards

Abdul Nazer
QBurst | www.qburst.com
Skype: nazerabdul

Isaac Murchie

da leggere,
2 set 2014, 06:05:0902/09/14
a Abdul Nazer, appium-...@googlegroups.com
Thanks. Have you set the "deviceName" capability?

Abdul Nazer

da leggere,
2 set 2014, 06:07:3802/09/14
a Isaac Murchie, appium-...@googlegroups.com
Hi Issac
Please ignore log in last email thread, that was mistakenly taken

Log having issue encountered is 

[TestNG] Running:

  /private/var/folders/hh/mjrld8g12h738zh0lchcgztr0000gp/T/testng-eclipse-1402985716/testng-customsuite.xml


FAILED CONFIGURATION: @BeforeMethod setUp

org.openqa.selenium.SessionNotCreatedException: A new session could not be created. (Original error: Required platform doesn't exist (API level >= 17)) (WARNING: The server did not provide any stacktrace information)

Command duration or timeout: 1.34 seconds

Isaac Murchie

da leggere,
2 set 2014, 06:09:0102/09/14
a Abdul Nazer, appium-...@googlegroups.com
What is in the Appium _server_ logs? Wherever you run the Appium server, there ought to be output that will provide us with more information.

Isaac Murchie

da leggere,
2 set 2014, 14:01:3602/09/14
a Abdul Nazer, appium-...@googlegroups.com
Please keep things on the Appium Discuss list.

I apologize for the delay. I have been on a plane for the past 7 hours.

Can you provide the _whole_ log? I would like to see where it is happening.

As a first thing, What versions of the Android sdk do you have installed? What is in ANDROID_HOME/sdk/platforms


On Tue, Sep 2, 2014 at 7:13 PM, Abdul Nazer <na...@qburst.com> wrote:
Hi Isac

I'm very new to appium, Sorry for the trouble

I hope this is the log we needed

debug: Error: Required platform doesn't exist (API level >= 17)

    at ADB.compileManifest (/Applications/Appium.app/Contents/Resources/node_modules/appium/node_modules/appium-adb/lib/adb.js:305:15)

    at null.<anonymous> (/Applications/Appium.app/Contents/Resources/node_modules/appium/lib/devices/android/selendroid.js:431:16)

    at /Applications/Appium.app/Contents/Resources/node_modules/appium/node_modules/async/lib/async.js:610:21

    at /Applications/Appium.app/Contents/Resources/node_modules/appium/node_modules/async/lib/async.js:249:17

    at iterate (/Applications/Appium.app/Contents/Resources/node_modules/appium/node_modules/async/lib/async.js:149:13)

    at /Applications/Appium.app/Contents/Resources/node_modules/appium/node_modules/async/lib/async.js:160:25

    at /Applications/Appium.app/Contents/Resources/node_modules/appium/node_modules/async/lib/async.js:251:21

    at /Applications/Appium.app/Contents/Resources/node_modules/appium/node_modules/async/lib/async.js:615:34

    at null.<anonymous> (/Applications/Appium.app/Contents/Resources/node_modules/appium/node_modules/appium-adb/lib/adb.js:111:9)

    at ChildProcess.exithandler (child_process.js:646:7)

debug: Responding to client with error: {"status":33,"value":{"message":"A new session could not be created. (Original error: Required platform doesn't exist (API level >= 17))","origValue":"Required platform doesn't exist (API level >= 17)"},"sessionId":null}


Rispondi a tutti
Rispondi all'autore
Inoltra
0 nuovi messaggi