Question

Not able to open Android native inbuilt (sms) app


Badge

Trying to automate messaging app with bellow mentioned capabilities and error logs

I have not included browser name capability but getting an error like do not mention both browser name and appPackage.

 

MutableCapabilities caps = new MutableCapabilities();caps.setCapability("platformName", "Android");caps.setCapability("deviceName", "Samsung_Galaxy_S9_free");caps.setCapability("appPackage", "com.samsung.android.messaging");caps.setCapability("appActivity", "com.samsung.android.messaging.ui.view.main.WithActivity");URL url = new URL("Driver creation url");AndroidDriver driver = new AndroidDriver(url, caps);

 

Error logs:

Exception in thread "main" org.openqa.selenium.SessionNotCreatedException: Could not start a new session. Response code 500. Message: errorId: fd8db18f-8562-4f24-b356-bbd77d3612c2 - Unable to allocate device Samsung_Galaxy_S9_free within 900000ms or 3 tries. This can happen if there were no available devices within the time or your plan's max concurrent test run is not corresponding to your usage


Detailed Info: Status Code: 500 - Error while starting appium session: {"value":{"error":"unknown error","message":"An unknown server-side error occurred while processing the command. Original error: The desired should not include both of an 'appPackage' and a 'browserName'","stacktrace":"UnknownError: An unknown server-side error occurred while processing the command. Original error: The desired should not include both of an 'appPackage' and a 'browserName'\n    at getResponseForW3CError (/root/appium/appium/1.22.2/node_modules/appium/node_modules/appium-base-driver/lib/protocol/errors.js:804:9)\n    at asyncHandler (/root/appium/appium/1.22.2/node_modules/appium/node_modules/appium-base-driver/lib/protocol/protocol.js:380:37)"}}
 


0 replies

Be the first to reply!

Reply