I am trying to run my script on iPHONE 5 which is connected to my windows machine. I am getting below error:
ERROR: debug: Appium request initiated at /wd/hub/session
info: Configuring Safari session
ERROR: debug: Request received with params: {"desiredCapabilities":{"browserName":"Safari","device":"iPhone 5s white"}}
info: Trying to use mobile safari, version 18
info: Looking for built in app MobileSafari
ERROR: error: xcode-select threw error Error: Command failed: 'xcode-select' is not recognized as an internal or external command,
ERROR: operable program or batch file.
ERROR:
info: Got configuration error, not starting session
ERROR: error: Stderr: 'xcode-select' is not recognized as an internal or external command,
ERROR: operable program or batch file.
ERROR:
ERROR: error: Stdout:
ERROR: error: Could not prepare mobile safari with version '18': Error: xcode-select threw an error
ERROR: error: Failed to start an Appium session, err was: Error: xcode-select threw an error
info: Cleaning up appium session
info: Error: xcode-select threw an error
at D:\QM_Work\AppiumForWindows-1.0.0\AppiumForWindows\node_modules\appium\lib\helpers.js:523:10
at ChildProcess.exithandler (child_process.js:641:7)
at ChildProcess.EventEmitter.emit (events.js:98:17)
at maybeClose (child_process.js:743:16)
at Process.ChildProcess._handle.onexit (child_process.js:810:5)
info: Responding to client with error: {"status":33,"value":{"message":"A new session could not be created. (Original error: xcode-select threw an error)","origValue":"xcode-select threw an error"},"sessionId":null}
POST /wd/hub/session 500 1379ms - 204b
As mentioned in the doumenations of Appium you need OSX to test iOS:
http://appium.io/slate/en/master/?ruby#toc_25
It is possible to run the tests from a windows machine but not the way you are probably thinking. You will still need a mac. Here are the requirements:
A mac on your network with Appium server running
Has Appium environment installed properly
Has the .app on the machine
If you have these three reqirements fulfilled and there is no firewall blocking network access to the mac then you can do it. You will have to actual tests on the windows machine but instead of specifying 127.0.0.1:8080 in the setup method as the IP address of Appium server you will replace it with this: yourmacsipaddress:8080 and this should execute the test properly.
Remember that you have to specify the path of the .app in the test which is running from your windows machine. But the catch is that the path has to be the path of the .app in the mac and not on your windows machine.
So the tests will run from your Windows machine but the installation of the app, the automation, and the testing will be done on the mac but you will get the "pass" or "fail" update on your Windows machine.
You cannot use Windows for iOS testing because Appium requires Instruments and some other native, OSX-only libraries to tell the phone what to do. (source)
Workarounds:
look into a mac mini hosting service, where you can run your iOS tests on a virtual machine.
buy a mac mini
Related
Unable to run the Chrome browser on Android by using Appium and RobotFramework
What I have tried so far:
*** Settings ***
Library AppiumLibrary
*** Test Cases ***
Loign_To_Weekend
App_Up_And_Run
*** Keywords ***
App_Up_And_Run
Open Application http://localhost:4723/wd/hub platformName=Android deviceName=RNNNNNNNK browserName=Chrome
Go To Url https://www.amazon.com/
but after installing appium settings app, not opening the chrome browser and it's showing error like below, both suggested links are invalid
WebDriverException: Message: An unknown server-side error occurred
while processing the command. Original error: No Chromedriver found
that can automate Chrome '10
2.0.5005'. You could also try to enable automated chromedrivers download server feature. See
https://github.com/appium/appium/blob/master/docs/en/writing-running-a
ppium/web/chromedriver.md for more details Stacktrace: UnknownError:
An unknown server-side error occurred while processing the command.
Original error: No Chromedriver found that can automate Chrome
'102.0.5005'. You could also try to enable automated chromedrivers
download server feature. See
https://github.com/appium/appium/blob/master/docs/en/writing-running-appium/web/chrom
edriver.md for more details
at getResponseForW3CError (C:\Users\abc\AppData\Roaming\npm\node_modules\appium\node_modules\appium-base-driver\lib\protocol\errors.js:804:9)
at asyncHandler (C:\Users\acb\AppData\Roaming\npm\node_modules\appium\node_modules\appium-base-driver\lib\protocol\protocol.js:380:37)
I'm not sure where I made the mistake, thanks for any kind of help
You must have chromedriver.exe in your Windows machine, for the correct version of Chrome in the Android phone.
You download the version for Chromedriver found that can automate Chrome '102.0.5005'.
You pass the path for chromedriver.exe to the Appium server, in the starting command or in capabilities.
On Appium Desktop, Advanced Tab, you find the Chromedriver Binary Path field.
Can some one help where our app is not showing in Appium inspector and even not working for Automation code in intellij after upgrade to Flutter driver version 3.0
getting error: Unable to create a new remote session. Please check the server log for more details. Original error: An unknown server-side error occurred while processing the command. Original error: Cannot read property 'match' of undefined
Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:17:03'
To fix this, Upgrade to appium-flutter-driver v1.7.0 with Appium 2 (2.0.0-beta.43 is the latest when I'm posting this)
Start Appium server using the command appium -p 4726 --base-path /wd/hub as sometimes starting server with default port was not working fine!
If you are not on Appium 2 already, check this guide for migration, I found it helpful
https://www.headspin.io/blog/migrating-to-appium-2-0-part-1-capability-prefixes
https://www.headspin.io/blog/installing-appium-2-0-and-the-driver-and-plugins-cli
I'm trying to setup a Xamarin UITest without any luck.
When I try to run 'all tests', I get the following error:
execute: C:\Users\Brandon\AppData\Local\Android\android-sdk\platform-tools\adb.exe devices - exit code: 1
error: could not install *smartsocket* listener: cannot bind to 127.0.0.1:5037: Only one usage of each socket address (protocol/network address/port) is normally permitted. (10048)
List of devices attached
adb server version (39) doesn't match this client (36); killing...
could not read ok from ADB Server
* failed to start daemon *
error: cannot connect to daemon
ADB seems to be started just fine and the weird thing is that it seems to be using an adb version from another user, even though..
1) Tools > Options > Xamarin > Android is set to different path than the above-mentioned, for the Android SDK.
2) There is no system environment path variable that I can find for the above-referenced adb.exe path!
Am I missing something?
In my case it was Android Emulator version mismatch. Somehow Emulator got updated to the newer version:
After uninstalling Emulator, switching Feed to Microsoft instead of google and re-installing Emulator - error was gone and everything worked just fine.
Hello I am trying to build my app on Mac but always get same error.
Error: An error occurred uploading to the build server
https://xxx.xxx.x.x:3000/cordova: Error: certificate is not yet
valid myAppp 1 Build
I wrote remotebuild start to command line on mac ant it is listening port 3000, What can I do to solve problem ?
When launching Appium, I get the following error:
ERROR: main.js: error: Unrecognized arguments:
SDK\adt-bundle-windows-x86_64-20140321\sdk\build-tools\android-4.4.2\LiftMaster_stg3_06132014.apk.
Running on a windowns 7 machine with a Android 4.4 connected and have Appium installed with node.js. Please help!
I solved it by adding quotation marks around the (Application path) because my windows username had a space in it.
You're getting that error because (if you're starting Appium from the command line) you're not passing the argument --app before the path to your .apk file.
$ appium path\to\app.apk
appium: error: Unrecognized arguments: path\to\app.apk.
versus the working:
$ appium --app path\to\app.apk
info: Welcome to Appium v1.1.0 (REV e433bbc31511f199287db7724e1ce692bcb32117)
info: Appium REST http interface listener started on 0.0.0.0:4723
info: socket.io started
info: Non-default server args: {"app":"path\to\app.apk"}
I got this error because my apk is place in folder with space. Remove space work for me ##
I met the same issue. There is a solution that can launch appium (UI) without error main.js
error: Unrecognized arguments.
Appium-General Setting-Logging, make sure "Quite Logging" isn't checked.
You can set and save your log on your Desktop( or other directories).
Then try to launch and run your appium script again. In my laptop, it can work well.
Even I had faced the same issue.
Try saving your apk on desktop and then give its path. It will work fine.