Appium: iOS - Java: [XCTestDriver managerProxy]: unrecognized selector sent to instance

[VTINFOJames]

The problem

XCUIElementTypeKeyboard is found however, the tests are unable to type text into XCUIElementTypeTextField with "setValue()" or "sendKeys()".

Test is finding the text field, reading it's default value, and able to click into the text field.

Environment

• Appium version (or git revision) that exhibits the issue: 1.6.3
• Desktop OS/version used to run Appium: OSX 10.12.3
• Node.js version (unless using Appium.app|exe): v5.0.0
• Mobile platform/version under test: iOS 10.3
• Real device or emulator/simulator: simulator
• Appium CLI or Appium.app|exe: Appium CLI

Details

I haven't ran this test since xCode 7.2 and iOS 9.1. I have just updated tests for XCUITest. Hopefully, I have everything configured properly. I followed the migration document. The Simulator option for "Connect Hardware Keyboard" is not selected. I have tried with IOSDriver, WebDriver and AppiumDriver with the same results.

Link to Appium logs

https://gist.github.com/VTINFOJames/527c90f1660271abb27144bbaac3da45.js

Code To Reproduce Issue [ Good To Have ]

`public static void signInScreen(AppiumDriver driver) throws InterruptedException {

    /* Method variables */
    String page = "Account";
    String testDesc = "SignIn_Screen"; 
    String userName = ConnectAs.MOBILE.getId();
String password = ConnectAs.MOBILE.getPw();
   MobileElement element;

    /* Ensure the screen opened is the Sign In screen */
    /* Note: The Sign In screen's UIANavigationBar has the name "Account" */
    try {
        assertEquals(page, driver.findElement(By.className("XCUIElementTypeNavigationBar")).getAttribute("name"));
    } catch (NoSuchElementException e) {
        CONSOLE.info("\t**** This is not the screen for the "+testDesc+" test! ****\n\t\tWe will     try signing out of the app.\n");
        MobileUISignOut.signOut(driver);
    }

    /* Test the UserName UIATextField */
    element = driver.findElement(By.className("XCUIElementTypeTextField"));
    element.click();
    if (!element.getText().equals("Username")) {
        element.clear();
    }
    assertEquals("Username", element.getText());

if (driver.findElement(By.className("XCUIElementTypeKeyboard")).isEnabled()) {
((IOSElement) element).setValue("test");
}
}`

[mykola-mokhnach]

There is a problem with WDA compilation. Try to build it manually using Xcode (probably you'll need to update it as well). WDA sources root is usually /usr/local/lib/node_modules/appium/node_modules/appium-xcuitest-driver/WebDriverAgent

[VTINFOJames]

I did an update and rebuild with no change in circumstance.

[mykola-mokhnach]

Do you mean you can build WDA with the default Xcode or you cannot?

Btw your logs are not accessible for me - can you double check the links? Also, it would be useful to have xcodebuild log as well, not only Appium log

[VTINFOJames]

I recreated my Appium log gist; not sure what happened there.
Here is the new link: https://gist.github.com/VTINFOJames/3d5cd71b01e4a40009821be0afbb1f9c
I did find that the Xcode build of WDA had the warning shown below so I will work on that.

[mykola-mokhnach]

still 404 for me :(
paste it here as a block - I'll try to read. Do not forget about xcodebuild log - that one is also important

Regarding the screenshot - this warning is expected, no need to worry.

[VTINFOJames]

I just edited the link and it now works but here it is as well: https://gist.github.com/VTINFOJames/3d5cd71b01e4a40009821be0afbb1f9c

[mykola-mokhnach]

ah OK, now I see. You are trying to execute your test on iOS 10.3. In that version Apple did some major updates to their framework, so it's not compatible with WDA snpashot included into Appium 1.6.3
Try to update Appium to 1.6.4-beta first and check whether it works then.

[VTINFOJames]

Will do. Thank you Mykola.

[VTINFOJames]

Okay. I'm still having the same issue with 1.6.4-beta. I am also unable to build WebDriverAgent.
Here is my appium log: https://gist.github.com/VTINFOJames/15b938bf33d53f1039bcb6cc48c2f373
, and here is my Xcode build log for WebDriverAgent.
https://gist.github.com/VTINFOJames/1bcc3b8db8d3c6e8485b3594b97d241a

[mykola-mokhnach]

Please report the error directly to WDA issues tracker https://github.com/facebook/WebDriverAgent/issues

[BasThomas]

Hey @mykola-mokhnach, it seems like this has been fixed in WDA. Any idea as to when there will be a new Appium beta that includes this fix?

[mykola-mokhnach]

@BasThomas It should be ok now: https://github.com/appium/appium/issues/8105

[rkandpal]

@mykola-mokhnach I am facing this issue on OSX 10.12.4 (appium 1.6.4-beta.2)
Environment -
Appium version : 1.6.4-beta.2
OS version : OSX 10.12.4
Node.js version : v6.9.2
Mobile platform under test : iOS 10.3
Real device or emulator/simulator : simulator
Appium CLI or Appium.app|exe : Appium CLI

Appium log:

[debug] [MJSONWP] Calling AppiumDriver.setValue() with args: [["[email protected]"],"D5C7DBDE-8470-48C3-8BB3-12163F363CB0","d0d33058-5293-4125-919a-bb05a98216b6"] [debug] [XCUITest] Executing command 'setValue' [debug] [JSONWP Proxy] Proxying [POST /element/D5C7DBDE-8470-48C3-8BB3-12163F363CB0/value] to [POST http://localhost:8100/session/47C1BBA9-387E-4A77-BC85-D1526F9FD5DE/element/D5C7DBDE-8470-48C3-8BB3-12163F363CB0/value] with body: {"value":["i","u","x","t","e","s","t","9","9","+","3","1","1","@","g","m","a","i","l",".","c","o","m"]} [debug] [JSONWP Proxy] Proxying [GET /element/D5C7DBDE-8470-48C3-8BB3-12163F363CB0/attribute/type] to [GET http://localhost:8100/session/47C1BBA9-387E-4A77-BC85-D1526F9FD5DE/element/D5C7DBDE-8470-48C3-8BB3-12163F363CB0/attribute/type] with no body [debug] [JSONWP Proxy] Got response with status 200: "{\n \"value\" : \"XCUIElementTypeTextField\",\n \"sessionId\" : \"47C1BBA9-387E-4A77-BC85-D1526F9FD5DE\",\n \"status\" : 0\n}" ( 0 CoreFoundation 0x0000000101270b0b __exceptionPreprocess + 171 1 libobjc.A.dylib 0x0000000100cd5141 objc_exception_throw + 48 2 CoreFoundation 0x00000001012e0134 -[NSObject(NSObject) doesNotRecognizeSelector:] + 132 3 CoreFoundation 0x00000001011f7840 ___forwarding___ + 1024 4 CoreFoundation 0x00000001011f73b8 _CF_forwarding_prep_0 + 120 5 WebDriverAgentLib 0x0000000112a3503e __29+[FBKeyboard typeText:error:]_block_invoke + 126 6 WebDriverAgentLib 0x0000000112a39a65 +[FBRunLoopSpinner spinUntilCompletion:] + 149 7 WebDriverAgentLib 0x0000000112a34e44 +[FBKeyboard typeText:error:] + 436 8 WebDriverAgentLib 0x0000000112a4362b -[XCUIElement(FBTyping) fb_typeText:error:] + 155 9 WebDriverAgentLib 0x0000000112a4eef2 +[FBElementCommands handleSetValue:] + 802 10 WebDriverAgentLib 0x0000000112a38b13 -[FBRoute_TargetAction mountRequest:intoResponse:] + 179 11 WebDriverAgentLib 0x0000000112a30134 __37-[FBWebServer registerRouteHandlers:]_block_invoke + 548 12 RoutingHTTPServer 0x0000000112ac6c18 -[RoutingHTTPServer handleRoute:withRequest:response:] + 136 13 RoutingHTTPServer 0x0000000112ac74fa __72-[RoutingHTTPServer routeMethod:withPath:parameters:request:connection:]_block_invoke + 47 14 libdispatch.dylib 0x000000010443d792 _dispatch_client_callout + 8 15 libdispatch.dylib 0x00000001044264e0 _dispatch_barrier_sync_f_slow_invoke + 292 16 libdispatch.dylib 0x000000010443d792 _dispatch_client_callout + 8 17 libdispatch.dylib 0x0000000104425247 _dispatch_main_queue_callback_4CF + 1041 18 CoreFoundation 0x0000000101235909 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 9 19 CoreFoundation 0x00000001011fbae4 __CFRunLoopRun + 2164 20 CoreFoundation 0x00000001011fb016 CFRunLoopRunSpecific + 406 21 Foundation 0x00000001007be480 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 274 22 Foundation 0x00000001007be35b -[NSRunLoop(NSRunLoop) run] + 76 23 WebDriverAgentLib 0x0000000112a2f026 -[FBWebServer startServing] + 262 24 WebDriverAgentRunner 0x000000011258b254 -[UITestingUITests testRunner] + 100 25 CoreFoundation 0x00000001011f8c6c __invoking___ + 140 26 CoreFoundation 0x00000001011f8b40 -[NSInvocation invoke] + 320 27 XCTest 0x00000001006898e2 __24-[XCTestCase invokeTest]_block_invoke_2 + 491 28 XCTest 0x00000001006c7f62 -[XCTestContext performInScope:] + 190 29 XCTest 0x00000001006896e4 -[XCTestCase invokeTest] + 254 30 XCTest 0x0000000100689fb2 -[XCTestCase performTest:] + 565 31 XCTest 0x0000000100687078 __27-[XCTestSuite performTest:]_block_invoke + 300 32 XCTest 0x0000000100686c68 -[XCTestSuite _performProtectedSectionForTest:testSection:] + 29 33 XCTest 0x0000000100686e4e -[XCTestSuite performTest:] + 214 34 XCTest 0x0000000100687078 __27-[XCTestSuite performTest:]_block_invoke + 300 35 XCTest 0x0000000100686c68 -[XCTestSuite _performProtectedSectionForTest:testSection:] + 29 36 XCTest 0x0000000100686e4e -[XCTestSuite performTest:] + 214 37 XCTest 0x0000000100687078 __27-[XCTestSuite performTest:]_block_invoke + 300 38 XCTest 0x0000000100686c68 -[XCTestSuite _performProtectedSectionForTest:testSection:] + 29 39 XCTest 0x0000000100686e4e -[XCTestSuite performTest:] + 214 40 XCTest 0x00000001006d3a86 __44-[XCTTestRunSession runTestsAndReturnError:]_block_invoke + 40 41 XCTest 0x0000000100695f27 -[XCTestObservationCenter _observeTestExecutionForBlock:] + 574 42 XCTest 0x00000001006d3925 -[XCTTestRunSession runTestsAndReturnError:] + 281 43 XCTest 0x0000000100671a50 -[XCTestDriver runTestsAndReturnError:] + 254 44 XCTest 0x00000001006cb86e _XCTestMain + 559 45 CoreFoundation 0x0000000101216b5c __CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK__ + 12 46 CoreFoundation 0x00000001011fbe54 __CFRunLoopDoBlocks + 356 47 CoreFoundation 0x00000001011fb5ee __CFRunLoopRun + 894 48 CoreFoundation 0x00000001011fb016 CFRunLoopRunSpecific + 406 49 GraphicsServices 0x00000001036c3a24 GSEventRunModal + 62 50 UIKit 0x00000001016940d4 UIApplicationMain + 159 51 XCTRunner 0x00000001005f188b XCTRunner + 6283 52 libdyld.dylib 0x000000010448665d start + 1 53 ??? 0x0000000000000005 0x0 + 5 ). Trying to apply a workaround... [debug] [BaseDriver] Set implicit wait to 0ms [debug] [BaseDriver] Waiting up to 0 ms for condition [debug] [JSONWP Proxy] Proxying [POST /element] to [POST http://localhost:8100/session/47C1BBA9-387E-4A77-BC85-D1526F9FD5DE/element] with body: {"using":"class name","value":"XCUIElementTypeKeyboard"} [debug] [JSONWP Proxy] Got response with status 200: {"value":{"ELEMENT":"4E80507D-9E70-4B0A-8085-6B09BF217E7E","type":"XCUIElementTypeKeyboard","label":null},"sessionId":"47C1BBA9-387E-4A77-BC85-D1526F9FD5DE","status":0} [debug] [XCUITest] Keyboard found. Continuing with text input. [debug] [BaseDriver] Set implicit wait to 1000ms [debug] [JSONWP Proxy] Proxying [POST /element/D5C7DBDE-8470-48C3-8BB3-12163F363CB0/value] to [POST http://localhost:8100/session/47C1BBA9-387E-4A77-BC85-D1526F9FD5DE/element/D5C7DBDE-8470-48C3-8BB3-12163F363CB0/value] with body: {"value":["i","u","x","t","e","s","t","9","9","+","3","1","1","@","g","m","a","i","l",".","c","o","m"]} [HTTP] <-- POST /wd/hub/session/d0d33058-5293-4125-919a-bb05a98216b6/element/D5C7DBDE-8470-48C3-8BB3-12163F363CB0/value 500 1350 ms - 5770 [HTTP] --> GET /wd/hub/session/d0d33058-5293-4125-919a-bb05a98216b6/screenshot {}

[mykola-mokhnach]

@rkandpal Make sure you have the same error while using the recent WDA source from master. Then report the issue directly to their project if it is still reproducible.

[johanblomgren]

We are also seeing the same issue as @rkandpal

[kirangowdawestwing]

We also have the same issue :

Appium fails with the below error.

Main reason :

XCUIElementTypeKeyboard is found however, the tests are unable to type text into XCUIElementTypeTextField with "setValue()" or "sendKeys()".
Test is finding the text field, reading it's default value, and able to click into the text field.

Environment
*Xcode version: 8.3

• Appium version (or git revision) that exhibits the issue: 1.6.4 beta 2
• Desktop OS/version used to run Appium: Mac OS Sierra
• Mobile platform/version under test: iOS 10.1, 10.2, 10.3 (Fails for all version)
• Real device or emulator/simulator: simulator

may be its related to latest update of Xcode.

Can anyone please update if they have ran into this kind of issue ?

[reuningATL]

We are having the same issue as @VTINFOJames and @rkandpal after updating my xcode to 8.3 and devices to 10.3. Waiting for a new build nightly build using 8.3 after our build server is done updating.

[pmck91]

Also having this issue on xcode 8.3 and ios 10.3

[WaFeIS7]

+1
having this issue on Xcode 8.3 and ios 10.3

[mykola-mokhnach]

There are two ways to solve the issue for now:

1. Reinstall appium beta to land the most recent xcuitest driver fixes
2. Download WebDriverAgent source from master and replace you local source at
   /usr/local/lib/node_modules/appium/node_modules/appium-xcuitest-driver/WebDriverAgent

[DVeautour]

Step 1 did not work for me. (installed 1.6.4-beta.2 on Friday.)
Step 2 did work for me, however, I needed to add the following line to WebDriverAgentLib/Commands/FBSessionsCommands.m:
#pragma clang diagnostic ignored "-Wdeprecated-declarations"
before:
NSURL *url = [NSURL URLWithString:urlString];

The pragma was in the original project file of the same name.

[reuningATL]

@DVeautour did you change the build target to 10.3? l am getting hung up on "Sending createSession command to WDA". It is building WDA but not launching.

[DVeautour]

Yes I did.

On Apr 3, 2017 12:29 PM, "reuningATL" [e-mail] wrote:

@DVeautour https://github.com/DVeautour did you change the build target
to 10.3? l am getting hung up on "Sending createSession command to WDA". It
is building WDA but not launching.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/appium/appium/issues/7829#issuecomment-291196724, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AMccAuki-rJ5EBo8zmuBNCHlusi-Hunkks5rsR5NgaJpZM4L7Q6i
.

[reuningATL]

@DVeautour Im still hanging up, are you tests running on real devices?

[DVeautour]

Yes, iPhone running 10.3.

[reuningATL]

@DVeautour If you don't mind, what was your process to get it running on 10.3? Was step 2 the only thing you did to get it working?

[DVeautour]

Installing the latest appium beta was needed as well.

[mitamallik]

I am seeing the same error:
(
0 CoreFoundation 0x0000000101270b0b __exceptionPreprocess + 171
1 libobjc.A.dylib 0x0000000100cd5141 objc_exception_throw + 48

Any idea what is the resolution? Running Appium 1.6.0 and just upgraded to Xcode : 8.3
It was working fine with xcode 8.2.1
Is there a resolution for this? Or is this issue still open? Will upgrading Appium help?

[WaFeIS7]

@mitamallik
It works for me

Download WebDriverAgent source from master and replace you local source at
/usr/local/lib/node_modules/appium/node_modules/appium-xcuitest-driver/WebDriverAgent

[mykola-mokhnach]

@mitamallik Simply updating WDA will not work, especially for such an old Appium version.

npm remove -g appium
npm install -g [email protected]

should do the job

[mitamallik]

Hi - Thanks for the feedback. Will this also update WDA? Or do I need to do
anything with that?

Thanks,
Mita

On Tue, Apr 4, 2017 at 12:01 PM, Mykola Mokhnach [e-mail]
wrote:

@mitamallik https://github.com/mitamallik Simply updating WDA will not
work, especially for such an old Appium version.

npm remove -g appium
npm install -g [email protected]

should do the job

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/appium/appium/issues/7829#issuecomment-291599631, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABQ9SiF5sEU5EJSy4CStRx1Y1JW71TU2ks5rspOTgaJpZM4L7Q6i
.

--
Madhumita Mallik
881 Persimmon Ave
Sunnyvale CA - 94087
408 730 9802

[mykola-mokhnach]

Yes, WDA will be updated together with appium

[DVeautour]

I had to update WDA from the source.

On Apr 4, 2017 4:05 PM, "mitamallik" [e-mail] wrote:

Hi - Thanks for the feedback. Will this also update WDA? Or do I need to do
anything with that?

Thanks,
Mita

On Tue, Apr 4, 2017 at 12:01 PM, Mykola Mokhnach >
wrote:

@mitamallik https://github.com/mitamallik Simply updating WDA will not
work, especially for such an old Appium version.

npm remove -g appium
npm install -g [email protected]

should do the job

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/appium/appium/issues/7829#issuecomment-291599631,
or mute
the thread
ABQ9SiF5sEU5EJSy4CStRx1Y1JW71TU2ks5rspOTgaJpZM4L7Q6i>
.

--
Madhumita Mallik
881 Persimmon Ave
Sunnyvale CA - 94087
408 730 9802 <(408)%20730-9802>

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/appium/appium/issues/7829#issuecomment-291616142, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AMccAqRUwUFK6dDUbif2qDO7c9SROmPiks5rsqKQgaJpZM4L7Q6i
.

[mykola-mokhnach]

@DVeautour appium beta automatically picks up the most recent module updates on install/reinstall and WDA has been recently updated there.

[DVeautour]

It didn't for me. Or maybe I did something wrong. I had to pull WDA after,
and add the pragma. Then it worked. Just saying...

On Apr 4, 2017 4:17 PM, "Mykola Mokhnach" [e-mail] wrote:

@DVeautour https://github.com/DVeautour appium beta automatically picks
up the most recent module updates on install/reinstall and WDA has been
recently updated there.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/appium/appium/issues/7829#issuecomment-291619212, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AMccAhhi_2xyr3yGdU9n4wewnQAAVwsiks5rsqVogaJpZM4L7Q6i
.

[antonys1]

@DVeautour it also didn't work for me. Can you explain your solution below please?

...pull WDA and add the pragma

[reuningATL]

@antonys1 I finally got it working. I removed my old appium installation, installed the beta using npm install -g [email protected]. I then got the WDA from the WDA project and replaced the one that came with appium. Ranbash Scripts/bootstrap.sh -d. But the biggest change I made was keeping all the code signing in WDA automatic. Also make sure to see if your libimobiledevice is up to date and that you have installed ios-deploy.

[antonys1]

@reuningATL thanks, I tried your approach but I didn't know what change you made to keep the code signing in WDA automatic, so I ran into a xcodebuild error status 65.

However, I did manage to get it working by cleaning the npm cache and creating a new terminal session for starting appium.

npm remove -g appium
npm cache clean
npm install -g [email protected]

[mitamallik]

Hi,
Can someone list out the steps for this that has it working all the time? I
see solutions posted and then someone replying that it works sometime for
them.

Thanks,
Mita

On Wed, Apr 5, 2017 at 7:13 AM, Sean Antony [e-mail]
wrote:

@reuningATL https://github.com/reuningATL thanks, I tried your approach
but I didn't know what change you made to keep the code signing in WDA
automatic, so I ran into a xcodebuild error status 65.

However, I did manage to get it working by cleaning the npm cache and
creating a new terminal session for starting appium.

npm remove -g appium
npm cache clean
npm install -g [email protected]

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/appium/appium/issues/7829#issuecomment-291874328, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABQ9SkCi-WZV2fJIJkfQm-bmf0PrwJlYks5rs6GdgaJpZM4L7Q6i
.

--
Madhumita Mallik
881 Persimmon Ave
Sunnyvale CA - 94087
408 730 9802

[imurchie]

All the latest of all systems shoudl be avaialble through the latest beta of Appium 1.6.4. Re-install and try.

[mitamallik]

So the following steps should work with xcode 8.3?

npm remove -g appium
npm cache clean
npm install -g [email protected]

Is there any need to install the WDA separately?

Thanks,

Mita

On Wed, Apr 5, 2017 at 9:17 AM, Isaac A. Murchie [e-mail]
wrote:

All the latest of all systems shoudl be avaialble through the latest beta
of Appium 1.6.4. Re-install and try.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/appium/appium/issues/7829#issuecomment-291914563, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABQ9SpVMvUmDNtUElvZ96tnF4fbTaKzOks5rs76XgaJpZM4L7Q6i
.

--
Madhumita Mallik
881 Persimmon Ave
Sunnyvale CA - 94087
408 730 9802

[imurchie]

There should be no need to maintain your own WDA.

[cyildirim]

It works for me after updated 1.6.4-beta and changed deployment target to ios device version.

[rcuyugan]

Didn't work: Remove Appium > upgraded to 1.6.4 > downloaded WDA > rebuild WDA > failed with same error. So frustrating!

Got response with status 200: {"value":"-[XCTestDriver managerProxy]: unrecognized selector sent to instance 0x1700562c0\n\n(\n\t0 CoreFoundation 0x0000000193306ff0 + 148\n\t1 libobjc.A.dylib 0x0000000191d68538 objc_exception_throw + 56\n\t2 CoreFoundation 0x000000019330def4 + 0\n\t3 CoreFoundation 0x000000019330af4c + 916\n\t4 CoreFoundation 0x0000000193206d2c _CF_forwarding_prep_0 + 92\n\t5 WebDriverAgentLib 0x000000010221bed4 __29+[FBKeyboard typeText:error:]_block_invoke + 136\n\t6 WebDriverAgentLib 0x0000000102220854 +[FBRunLoopSpinner spinUntilCompletion:] + 172\n\t7 WebDriverAgentLib 0x000000010221bcbc +[FBKeyboard typeText:error:] + 372\n\t8 WebDriverAgentLib 0x000000010222a284 -[XCUIElement(FBTyping) fb_typeText:error:] + 168\n\t9 WebDriverAgentLib 0x00000001022354c0 +[FBElementComman...
[debug] [JSONWP Proxy] Proxying [GET /element/10E486A3-634F-40BB-A2B4-A9C232D74E62/attribute/type] to [GET http://localhost:8100/sessi

[aljones15]

upgraded to 1.6.5-beta fixed it after unistall and cache clean

[Kavitha14manoj]

Following steps worked for me on iOS 10.0.2
npm remove -g appium
npm cache clean
npm install -g [email protected]
/usr/local/lib/node_modules/appium/node_modules/appium-xcuitest-driver/WebDriverAgent
rm -r WebDriverAgent
set the path /usr/local/lib/node_modules/appium/node_modules/appium-xcuitest-driver
Download or clone WDA https://github.com/facebook/WebDriverAgent
cd ~/WebDriverAgent
./Scripts/bootstrap.sh
open WebDriverAgent.xcodeproj
Open WebDriverAgent.xcodeproj in Xcode. For both the WebDriverAgentLib and WebDriverAgentRunner targets, select "Automatically manage signing", and then select your Development Team. This should also auto select Signing Ceritificate.

[rcuyugan]

Installed desktop version. Fixed all my issues.

Sent from my iPhone

On May 1, 2017, at 1:37 AM, Andrew Jones [e-mail] wrote:

upgraded to 1.6.5-beta fixed it after unistall and cache clean

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

[mitamallik]

Hi,
So I will be upgrading my Appium.
So are these the steps I need to execute to run with Xcode 8.3.1?

npm remove -g appium
npm cache clean
npm install -g [email protected]

Is this all?
Or do I need these steps
npm remove -g appium
npm cache clean
npm install -g [email protected]
/usr/local/lib/node_modules/appium/node_modules/appium-xcuitest-driver/WebDriverAgent
rm -r WebDriverAgent
set the path /usr/local/lib/node_modules/appium/node_modules/appium-xcuitest-driver
Download or clone WDA https://github.com/facebook/WebDriverAgent
cd ~/WebDriverAgent
./Scripts/bootstrap.sh
open WebDriverAgent.xcodeproj
Open WebDriverAgent.xcodeproj in Xcode. For both the WebDriverAgentLib and WebDriverAgentRunner targets, select "Automatically manage signing", and then select your Development Team. This should also auto select Signing Ceritificate.

[wluu]

Don't know if this is helpful, but [email protected] (current release) fixed this issue for me. One thing to note though is that I'm using appium as a node module in my project i.e. npm install appium; not a global install.

My environment:
OS: macOS 10.12.4
Xcode: 8.3.2
iOS Simulators: iphone 7 10.2 and 10.3
Node: 6.10.3

[lock[bot]]

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.