Protractor doesn't support angular synchronization on iOS

[barmy-tester]

This issue is similar to #1736

I cannot run my tests on iOS real device using appium and protractor. Tests fail each time with following errror: 'ERROR running appium command: Cannot assign to read only property X of true' where X is 'random' digit.
I've tried many configuration varieties, etc. and still got the same error.
The only workaround is to turn of synchronization by adding ignoreSynchronization=true to my tests. But with such workaround there is no point to use protractor anymore.

Here are instructions to integrate iOS with Safari, Appium and protractor:

• git clone appium
• intialize appium by running:

  ./reset.sh --ios --real-safari --profile '34e19aa1-xxxx-xxxx-xxxx-xxxxxxxxx' --verbose

• run webproxy:

  ./bin/ios-webkit-debug-proxy-launcher.js -cXXXXXXXXXXXXXXX -d

• start appium server:

  node lib/server/main.js -U XXXXXXXXXXXXXXXXXXXXXXXXXXX

• run test by executing:

  protractor test.conf.js

You can find test.conf.js, appium console output and protractor console output in attached.
I've also tried to run tests with selenium grid by registering iOS node and the result was the same

Versions:

• OSX El Capitan, 10.11.12
• Xcode 7.2
• Appium 1.4.16
• Protractor 3.0.0
• node 5.4.0
• npm 3.3.12
• DUT iOS version 9.2

If you need any additional information please let me know.

Just FYI, I can successfully run the same script with similar configuration on Windows - IE, Firefox, Chrome and Android - Chrome - real device

appium_output.txt
protractor_output.txt
test.conf.js.txt

[juliemr]

Assigning to @sjelin - we're hoping to refresh mobile docs/setup soon.

[ivarcegeka]

I have the same problem. I have a simple cordova application and some simple tests. The tests work perfectly in the browser and on Android, but in iOS I get the error: 'Failed: ERROR running Appium command: Cannot assign to read only property '1' of true'. I will attach the protractor config and the test.
I'm starting appium from the Appium.app. The only setting I changed from the default settings is that I checked 'use native instruments'.

Am I doing something wrong or is this a bug?

protractor-ios.config.txt
uitest.spec.txt
appium_log.txt
protractor_log.txt

[wswebcreation]

Did you got this working on iOS simulator?
We faced the same problem, but in our opinion it's more a Appium issue then a Protractor issue. It looks like the returnedFromExecuteAtom is forcing a 'stop for alerts'. appium/lib/devices/ios/ios-controller.js:692

We are looking into it further

[ivarcegeka]

Nope, not yet.

[ivarcegeka]

I upgraded my Appium version to 1.5 (from 1.4.13) and now I don't get those errors anymore. I get different errors though. It seems as if the click doesn't work, but that is a different problem.

[premkh9]

I am using Appium 1.4.13 and Xcode 7.2 but I am not able to execute any of my tests in IOS simulator. Issue persists in Sauce labs emulator as well

Job Details - https://saucelabs.com/beta/tests/f3bb551a0daf4f5d9d867b71e9b29657
multiCapabilities: [{
'browserName': 'Safari',
'appium-version': '1.4.13',
platformName: 'iOS',
platformVersion: '9.2',
deviceName: 'iPhone 6 Plus',
'name': 'Protractor Job',

[teddyhwang]

I'm wondering if this is the issue: https://discuss.appium.io/t/protractor-safari-tests-broken-on-ios-9/7354

[premkh9]

Hi Sjelin, any resolution to resolve the issue

[sjelin]

Yeah, I'm working on it. Hopefully I'll have something in next week, but we'll see.

[premkh9]

Hi Sjelin, Hope you are doing good ! Did you get a chance to look into the issue?

[sjelin]

I did! I got wrapped up in other things though. Hopefully before the end of this week I'll have something for you 😄

[barmy-tester]

Any news?