appium / appium-ios-device Goto Github PK

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

appium-ios-device related thing (if needed)

https://github.com/doronz88/pymobiledevice3/blob/master/misc/RemoteXPC.md

We should send message via the RemoteXPC, remoted. We maybe detect if it is necessary by checking the response of UsesRemoteXPC
https://github.com/doronz88/pymobiledevice3/blob/master/misc/RemoteXPC.md#remotexpc-services

axiois is used in lib/imagemounter/utils/list_developer_image.js but it's not added to the package.json

The getDeviceTime method fetches the time using plist services,
when fetching the utcOffset for the devices it breaks with an exception:

Encountered internal error running command: Error: Unexpected data: {"Key":"TimeZoneOffsetFromUTC","Request":"GetValue","Value":0}
     at Lockdown.getValue (/usr/local/appium_1.15.0/node_modules/appium-ios-device/lib/lockdown/index.js:85:13)

Ways to reproduce:

• use on any appium greater than and equal to 1.15 on real devices in GMT+0 timezone region
• driver.device_time

Reason:
This doesn’t happens usually, but for devices in UTC zone because, here the actual TimeZoneOffsetFromUTC is 0 as they fall in the GMT zone.
causing this check to fail as data.value is actually 0, thus raising an exception.

iphone supports enable and disable of assistive touch by parsing boolean to com.apple.Accessibility.AssistiveTouchEnabledByiTunes

tools like tidevice already implemented and it is nice to have in webdriveragent with api control.

Adapted from https://github.com/YueChen-C/py-ios-device to https://github.com/appium/appium-ios-device
I have completed 90% of the work for the instruments protocol. And the test is successful above version 14. you can get fps, performance, netstat, etc.
but i have a problem on devices under version 14. After the ssl protocol is successfully handshake, I need to close the ssl protocol channel and use clear text transmission. I searched a lot of information, but I couldn't succeed.

Python:
https://github.com/YueChen-C/py-ios-device/blob/71267a1ac472db53fa84497312f0a4cdc0fdee17/ios_device/servers/Instrument.py#L29

nodejs:
https://github.com/YueChen-C/appium-ios-device/blob/b6f0fb42258f04ecc28509f756b089412b440db8/lib/services.js#L89

@KazuCocoa @mykola-mokhnach Could you spare some time to help me ？

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.