New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problems setting up appium-1.6.0-beta1 for XCUITesting #6759
Comments
I'm not sure that Appium can do anything about the rate limiting. The webpack error is avoidable by using the When you say you could not reproduce the issue above, which issue are you referring to. |
The problem with rate limiting is that running the script manually resulted in a build that appium was able to use, even though it still generated log messages about rate limiting. Maybe the script is returning an error status where it shouldn't, and Appium is treating it as a fatal error. My bad, I missed the I was about to edit the issue, but shortly after submitting it I realized that the |
Interesting. I'll look into how to test that. If peertalk has really failed to download, I don't think you would be able to test on a real device. |
I haven't had a chance to look into real device testing, which might be why I haven't run into any issues with it yet. I'll keep you updated if I find a solution on my end. |
I modified the |
@ssynix @imurchie can you please let me know. |
You will need Carthage installed, and libimobiledevice. See https://github.com/appium/appium-xcuitest-driver#external-dependencies |
I followed @ssynix procedure and finally got the below error in terminal [XCUITest] 2016-08-29 14:45:44.980 xcodebuild[4493:60451] Connection peer refused channel request for "dtxproxy:XCTestManager_IDEInterface:XCTestManager_DaemonConnectionInterface"; channel canceled <DTXChannel: 0x7fd0d5311b60> [XCUITest] [XCUITest] ./Scripts/generate_modules.sh: line 15: Modules/module.modulemap: Permission denied The following build commands failed: [XCUITest] xcodebuild exited with code '65' and signal 'null' |
@triager please label: Bug |
@SrinivasanTarget my problems have all been resolved (at least the ones in the original post). It was all user-error on my end except the API rate limit being reached using carthage, which I filed here: facebookarchive/WebDriverAgent#260. |
@ssynix could you please help me out how i can run appium 1.6.0 beta 1 on iOS 10 simulator using java client. |
Here are the log details for my current issue. I am using Appium 1.6.0beta1 with java for execution. XCUITest] Using default agent: /usr/local/lib/node_modules/appium/node_modules/appium-xcuitest-driver/WebDriverAgent/WebDriverAgent.xcodeproj [XCUITest] Using default bootstrap: /usr/local/lib/node_modules/appium/node_modules/appium-xcuitest-driver/WebDriverAgent [XCUITest] Launching WebDriverAgent on the device [XCUITest] Error: Command '/bin/bash Scripts/bootstrap.sh -d' exited with code 1 [XCUITest] Shutting down WebDriverAgent |
@THIRISANGU please run ./Scripts/bootstrap.sh in the WebDriverAgent folder, which may resulted in sh: webpack: command not found. Then resolved it by npm i -g webpack. Then please let us know your feedback. |
If you run (as Appium does) The underlying problem is a permissions one. This is something that you'll have to resolved locally. |
meet same.
Result of request is:
after that in same folder did:
and got it WORKING :-) |
You should not need to run that command manually under normal conditions. Appium will do so automatically. In a release later this morning we will have better logging for people who don't have Carthage installed. |
I am getting the same error, while upgrading to appium 1.6.0-beta1 version.
|
please share what exact version I have to install and when will we get the stable build, I am getting stuck here as my app is fully upgrade according to xcode8 with latest swift and OS version, but Appium version some how not supported. PS: Also, Please ASAP app version as well. Thanks |
You need to upgrade homebrew.
And then retry installing Carthage. |
Hey @imurchie , thanks for reply, I update it, now I got below error ; To resolve below error I run above suggested command (chmod: /Users/F2849/.npm-packages/lib/node_modules/appium/node_modules/appium-xcuitest-driver) then got error : No such file or directory Also I got the idea, why it showing No file directory as I m not having .npm-package directory in my local machine. WebDriverAgent f2849$ ./Scripts/bootstrap.sh -d |
I am not sure where you got that command. But the path is to someone else's installation. You appear to have appium installed in So you need to change the permissions or ownership on that tree. |
for command its a typo error from my side, sorry for that, so for providing permission I used command : sudo chmod -R 777 /Users/F2849/.npm-packages/lib/node_modules/appium/node_modules/appium-xcuitest-driver/ (Please refer @Hellengo comment on #6853 (comment) ) |
And there is still a problem? |
Yes |
Hello @imurchie , I have observed one more point as well, plz check my highlighted log points below as I mentioned launch timeout around 90000 in my script but appium 1.6.0 version shows default timeout is 6000ms, I checked it with older appium version it working as per launch timeout is given on the script(might be I m wrong but I think their might be an issue): [Appium] Creating new XCUITestDriver session |
The launch timeout is the launch of the app, not the simulator. The timeout should not affect things, unless the sim is actually not opened. The issue is still that you don't have permission to write to |
I'm using Appium 1.6.0 and getting the following error every time I try to run any of my test cases: [MJSONWP] Encountered internal error running command: Error: Command '/bin/bash Scripts/bootstrap.sh -d' exited with code 1 I'd love to get any feedback on what could be causing this! Here is the whole log (I've cleansed various unique identifiers with 000's): [Appium] Welcome to Appium v1.6.0 |
I saw this as well. The error also gives the solution. 'XCUITest] Carthage not found. Install using brew install carthage' |
I saw that too and installed Carthage with brew then re-ran and the same error occurred. I wonder if I have to do some special Carthage installation option to get it to install in a specific location for Appium? My understanding of Appium 1.6.0, though, is that Appium is supposed to take care of any required Carthage installation for you. |
@lvconley The only requirement there is that carthage executable should be in PATH and it is visible to Appium server. Type in Terminal
and check the output is not empty. |
Thanks guys, is working now! My initial install attempts were not working correctly with Brew, and I kept getting warnings or errors which indicated that the installation may not have fully worked correctly. So, I ran the following command to see what had been installed by brew: brew list And carthage was never listed. So, I did an update of Brew just to make sure I had the latest version: brew update And actually encountered permissions errors which I temporarily resolved with brute force: chmod -R 777 /usr/local and this allowed the next 'brew update' attempt to complete without any errors. Once brew had been fully updated, the next time I ran: brew install carthage The installation completed without any warnings or errors and then when I ran the following command at the terminal: which carthage The carthage installation path was instantly displayed. And then I re-ran my test code, and the test worked perfectly! Thanks for the tips guys, very helpful!! |
I have done all setup which are mentioned in the following link. I am in "Real devices>>Configuration>>Manual configuration alternative>> WebDriverAgent needs to be built with development team---- Thanks in advance. |
@kirangowdawestwing I ran into a couple of issues initially. Since the driver was in beta at the time, I'm not even sure if they're still relevant. My issues were resolved in the first 5 comments. For the API rate-limiting issue, one of my coworkers mentioned that Carthage downloaded the dependencies from a mirror after failing to download them from github. That wasn't the case for me so I submitted a PR to WDA to make |
I have finished with the Certificate signing. When I run the
Running tests... |
Something is broken in your installation. It is not |
i am following the following link for the installation steps.
|
You should not need webpack at all. I would re-install the |
MDMCreateDeltaDirectory:1920 calling MDMDirectoryDiff with: Testing failed: Now I am getting this error. how to get the KissXML.framework/KissXML |
The KissXML framework is downloaded when the |
In Integration App >> 'Provisioning profile' signed code is deprecated. |
I have done all the signing certificate configurations in Xcode 8.1. But when I execute the following command |
Hi, I am unable to launch the iOS simulator in Appium 1.6.2 version. it shows an error like killing all simulator. |
@kommuswamy this is not related issue, can you open new issue with all the necessary details as mentioned in issue template ? |
@kommuswamy , please increase app launch time. |
I am getting the same error After running:
I ran the When I navigate to
I have carthage version 0.18.1 installed, running Appium 1.6.3 with ios10.1 and xcode 8.1 on osx 10.11.6 |
I have a similar problem as @dayanacgeorge using WebDriverAgent that came with Appium 1.6.3 , so I pull the latest version from GITHub https://github.com/facebook/WebDriverAgent and re-built it and I got it working, I suggest replace all files from Appium version with latest files on GIT Hub repro, and rebuild, https://www.youtube.com/watch?v=Yi177Si5aLU#t=3.478444 is a good video to check for all dependencies |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
The problem
I ran into a couple of issues setting up the 1.6.0-beta1 driver for iOS 10 simulator testing with the XCUITestDriver.
It mentions that it has a problem reading a zip archive. I looked into it and realized that the zip archive is actually this text file:
Probably because of how our internal corporate network works.
I ran
./Scripts/bootstrap.sh
in theWebDriverAgent
folder, which resulted insh: webpack: command not found
. I resolved it bynpm i -g webpack
.Afterwards, the
bootstrap.sh
script finished the build successfully, even though it printed one error and it still mentioned that it skipped downloading packages due to an API limit being reached.I managed to trigger the creation of an iOSDriver (instead of XCUITest) on my first almost successful attempt, which led to:
I don't recall changing anything in my config, but I couldn't reproduce the issue above.
After all this, I managed to run the app on the iOS 10 simulator and execute some basic commands.
Environment
The text was updated successfully, but these errors were encountered: