iOS test with Appium, problems when starting inspector (i)

Recently in the company, let do iOS automated testing, because previously did Android automated testing, with the appium, feel nothing, the results of the first in the environment encountered a lot of problems, now will I encounter problems, and solutions, to share it. (PS: Spit trough a bit testhome, sent two posts a question post a share of comments, all to pull to the offending area, the problem is not to see)

Get to the point and say something about my environment:

Xcode 7.1.1

Simulator 9.1

Appium 1.4.13

iphone 5s ios9.1

First of all, Appium in the iOS version Select this piece of the highest version to 8.4, maybe everyone will have doubts, I am 9.1 no option to do AH.

This problem is very good to solve, we take a closer look at the settings in the text box can be entered manually, you can enter the keyboard, Ah, enter after you check the following settings IOS setting->advanceed->use Native Instruments Libra Ry, or developer Settings Check the Enable, Custom Server Flags and join the--native-instruments-lib please refer to: https://discuss.appium.io/t/ Has-anyone-been-able-to-use-ios-simulator-9-1-with-appium-1-4-13/6887/8

Probably the problem that we often see is this, found that after starting the inspector, the package also installed to simulator but the application has been started on the flash, the problem is because iOS non-cross-platform, compile time must be specified to run on arm or x86. The difference in packaging is that the SDK used differs. The solution to this problem is to use Xcode to install the package on the phone virtual machine directly and then start the inspector. (I have a problem here, but I chose to use Bundleid when I started, I was prompted that I could not find the package.) When using the app Path Discovery package is installed, it will not be re-installed, will directly start the installed package)

During the use of the virtual phone test, when using SendKeys to adjust the input method, may be error: ' An error occurred while executing user supplied JavaScript This problem I only encountered on the virtual phone, the real machine test did not encounter this situation. may not be able to adjust the input method caused.

The following is the use of the real machine to start the inspector, the problem encountered, the real machine startup encountered problems, first put a log

Info: [Debug] [INST STDERR] 2015-12-11 17:54:01.261 instruments[10308:11044258] WebKit threading violation-initial use O F WebKit from a secondary thread.

Info: [Debug] [INST STDERR] 2015-12-11 17:54:07.289 instruments[10308:11044422] Attempting to change event horizon while D Isengage

Info: [Debug] [INST STDERR] Instruments Trace Error:target failed to run:the operation couldn ' t is completed. (Fbsopenapplicationerrordomain error 3.) : Failed to launch process with bundle identifier ' Com.zipingfang.1 '
Info: [Debug] [INST STDERR] 2015-12-11 17:54:07.289 instruments[10308:11044241] Attempting to change event horizon while D Isengage

Info: [Debug] [Instserver] Instruments exited with code 253
Info: [Debug] Killall Instruments
Info: [Debug] Instruments crashed on startup
Info: [Debug] Attempting to retry launching instruments, the IS retry #1
Info: [Debug] Killall IOS Simulator

Yes, that's Instruments crashed. This problem was not solved until today, the following points should be noted for iOS testing using a real machine:

Reference: HTTPS://DISCUSS.APPIUM.IO/T/IOS-INSTRUMENTS-CRASHED-ON-STARTUP/1191/14

1. To have a developer account

2. The device has been added to the developer device

3. Install apps to your phone using Xcode debug
4. A certificate in the description file that trusts this app
5. In the phone settings-Developer, tick use UI Automation.

will continue to update if not welcome

　　

iOS test with Appium, problems when starting inspector (i)