Unable to connect Appium Inspector to session with Bitbar device
Hello, I'm trying to connect Appium Inspector to a device on Bitbar, but it always returns an error: "Failed to create session. Request timed out" or "Failed to create session. All non-standard capabilities should have a vendor prefix. The following capabilities did not have one: source". Am I passing some wrong parameter, or missing something? Caps: { "appium:bitbar_device": "Apple iPhone 12 Pro Max A2411 16.0", "platformName": "iOS", "appium:bitbar_app": "201000000", "appium:bundleId": "br", "appium:newCommandTimeout": "8000", "appium:automationName": "XCUITest", "appium:autoGrantPermissions": "true", "appium:autoDismissAlerts": "true", "appium:bitbar_frameworkId": "900", "appium:bitbar_testTimeout": "8000" } Can anyone help me?Solved436Views0likes1CommentBitbar appium mid-session app install/upgrade
I want to create an automated test on Bitbar that will run an Appium driver with an app normally, and mid-session will update the app to a newer version. I searched the docs and didn't find a reference for something like this. any info would be helpful. Thank you everyone in the community393Views0likes0Commentscom.testdroid.api.APIException: Failed to submit test run! No device model matching pattern
I'm New to bit-bar. I'm trying to automation mobile native application, When run my test case with below desired capabilities, I'm getting Message: com.testdroid.api.APIException: Failed to submit test run! No device model matching pattern '%Samsung Galaxy A50 2019 SM-A505FN' available My Desired capabilities: {"bitbar_apiKey": "<my Key>", "bitbar_device": "Samsung Galaxy A50 2019 SM-A505FN", "bitbar_app": "<my app id>", "platformName": "Android", "appPackage": "com.aws.android", "appActivity": "app.ui.HomeActivity", "deviceName": "Android Phone", "bitbar_project": "WB-BitBar-POC", "bitbar_testrun": "Scree", "automationName": "uiautomator2", 'appPackage': 'com.aws.android', 'appActivity': 'app.ui.HomeActivity'} I have tried both driver = webdriver.Remote("https://us-west-mobile-hub.bitbar.com/wd/hub", capabilities) and browser.driver = webdriver.Remote("https://appium.bitbar.com/wd/hub", capabilities) Any help on this would be appreciated.669Views0likes0CommentsUnable to create a session using Appium
Hi, I've got issues while trying to set up Android automated tests with Automation Testingservice. Through my local Java Appium project, whenever I try to create new instance of AndroidDriver, the server responds with following error: org.openqa.selenium.SessionNotCreatedException: Unable to create a new remote session. Please check the server log for more details. Original error: org.apache.http.client.ClientProtocolException (WARNING: The server did not provide any stacktrace information) Command duration or timeout: 1.67 seconds Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:17:03' System info: host: '…', ip: '…', os.name: 'Mac OS X', os.arch: 'x86_64', os.version: '10.16', java.version: '1.8.0_281' Driver info: driver.version: AndroidDriver Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:17:03' System info: host: '…', ip: '…', os.name: 'Mac OS X', os.arch: 'x86_64', os.version: '10.16', java.version: '1.8.0_281' Driver info: driver.version: AndroidDriver at io.appium.java_client.remote.AppiumCommandExecutor$1.createSession(AppiumCommandExecutor.java:216) at io.appium.java_client.remote.AppiumCommandExecutor.createSession(AppiumCommandExecutor.java:225) at io.appium.java_client.remote.AppiumCommandExecutor.execute(AppiumCommandExecutor.java:250) at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:552) at io.appium.java_client.DefaultGenericMobileDriver.execute(DefaultGenericMobileDriver.java:41) at io.appium.java_client.AppiumDriver.execute(AppiumDriver.java:1) at io.appium.java_client.android.AndroidDriver.execute(AndroidDriver.java:1) at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:213) at io.appium.java_client.AppiumDriver.startSession(AppiumDriver.java:363) at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:131) at io.appium.java_client.DefaultGenericMobileDriver.<init>(DefaultGenericMobileDriver.java:37) at io.appium.java_client.AppiumDriver.<init>(AppiumDriver.java:89) at io.appium.java_client.AppiumDriver.<init>(AppiumDriver.java:99) at io.appium.java_client.android.AndroidDriver.<init>(AndroidDriver.java:97) … I've tried to contact Appium server "manually" but ended with not much informations regarding the cause: { "sessionId": null, "message": "org.apache.http.client.ClientProtocolException", "value": { "message": "org.apache.http.client.ClientProtocolException", "origValue": "org.apache.http.client.ClientProtocolException" }, "status": 33 } The project is using Appium java-client 7.6.0as Maven dependency. I've also checked that there are no conflicts regarding HttpClient dependency (using same as java-client's which is 4.5.13). Capabilities used are the ones recommended while completing the form here:https://cloud.bitbar.com/#testing/test-run-creator { "bitbar_appiumVersion": "1.22.3", "bitbar_description": "Implementation of BitBar in stack", "bitbar_testrun": "Implementation test", "noReset": "true", "bitbar_testTimeout": "1200", "bitbar_target": "android", "deviceName": "Android Device", "fullReset": "false", "bitbar_locale": "FR", "bitbar_apiKey": "<my-api-key>", "automationName": "Appium", "bitbar_app": "<my-app-id>", "platformName": "Android", "bitbar_device": "Google Pixel 3a Android 12", "bitbar_project": "MyProject" } Targeted Appium server is this one:https://eu-mobile-hub.bitbar.com/wd/hub/ Since there are no informations returned from the server, could anyone provide a bit of help regarding this matter ? Thanks a lot.1.2KViews0likes1CommentUnable to connect to BitBar via automation script using appium + NodeJS + WebdriverIO
Hello team, We are trying to connect to smartbear - bitbar for mobile automation using nodeJS - wdio5. Since this is for automation POC we are using the config file from: https://github.com/bitbar/test-samples/blob/master/samples/testing-frameworks/appium/client-side/javascript/webdriver.io/wdio.conf.js While connecting we are getting error as : [0-0] 2022-08-24T16:18:54.762Z WARN webdriver: Request failed due to <html> <head><title>405 Not Allowed</title></head> <body> <center><h1>405 Not Allowed</h1></center> <hr><center>nginx/1.21.6</center> </body> </html> [0-0] 2022-08-24T16:18:54.762Z INFO webdriver: Retrying 1/3 2022-08-24T16:18:54.762Z INFO webdriver: [POST] https://cloud.bitbar.com/#testing/dashboard:443%5Cwd%5Chub%5Csession Can anyone suggest how to correct this? Appreciate any help1KViews0likes3CommentsUnable to connect Appium Inspector(Web version) to session with Bitbar device
Hi Team, I am trying to connect to bitbar device usinghttps://inspector.appiumpro.com/using my local Appium server.But it is throwing error. Can anyone tell me what I am missing here. host:127.0.0.1port:4723 remote path:/wd/hub ssl-unchecked Advanced settings: Allow Unauthorized Certificates-checked Gave BITBAR API key Desired capabilities given: { "bitbar:options": { "bitbar_device": "LG Google Nexus 5 6.0.1", "bitbar_app": "********",//got the id from bitbar after uploading the .apk file "bitbar_target": "android", }, "platformName": "Android", "appium:deviceName": "Android Phone", "appium:automationName": "Appium" } mote806Views0likes1CommentApp Automation :How to Set Google Play Store credentials using Capabilities in bitbar?
App Automation 1.How to Test Google in-app purchase flows 2.How to Test accepting payments using Google Pay 3.How to Test production version of your apps by downloading it from Google Play Store609Views0likes0CommentsHow to find test run id by session id
Hi, When we run the client-side Appium test we get session id as an identifier of our test, but if we want to update the test display name or something else via REST API we need to use runID (https://cloud.bitbar.com/cloud/swagger-ui.html#/Test%20Results/updateUserTestRunUsingPOST),so the question is how to find out runID for client-side runs? can we somehow map the session id to the remote runID? Thanks for response1.8KViews1like0Comments