fastmonkey,xcode10.1,iOS13.5 系統,啟動後崩潰
command line tools 是用的 xcode10.1 的,將 13 系統的 diskimage 放到了 10.1 的 xcode 目錄下之前是 OK 的,後來好像是 13.4 開始啟動後就閃退了,有哪位大大遇到過這個問題嗎?有木有解決方案?
2020-06-02 12:50:18.766530+0800 XCTestWDUITests-Runner[1424:625693] Running tests...
Test Suite 'All tests' started at 2020-06-02 12:50:23.293
Test Suite 'XCTestWD.framework' started at 2020-06-02 12:50:23.296
Test Suite 'XCTestWD.framework' passed at 2020-06-02 12:50:23.298.
Executed 0 tests, with 0 failures (0 unexpected) in 0.000 (0.002) seconds
Test Suite 'XCTestWDUITests.xctest' started at 2020-06-02 12:50:23.300
Test Suite 'XCTextWDRunner' started at 2020-06-02 12:50:23.301
Test Case '-[XCTestWDUITests.XCTextWDRunner testRunner]' started.
t = 0.00s Start Test at 2020-06-02 12:50:23.304
t = 0.04s Set Up
t = 0.05s Pressing Home button
t = 62.18s Open com.HuaXiaBank.HuaCard
catching internal failure: Unable to update application state promptly for Application 'com.HuaXiaBank.HuaCard'. in file: /Users/chenrui/Desktop/testProgramm/Fastmonkey/Fastmonkey/XCTestWD-master/XCTestWD/XCTestWDUITests/XCTestWDRunner.swift at line: 38
t = 62.29s Launch com.HuaXiaBank.HuaCard
t = 62.48s Wait for accessibility to load
t = 62.50s Wait for com.HuaXiaBank.HuaCard to idle
t = 64.67s Find the Application 'com.HuaXiaBank.HuaCard'
t = 64.68s Snapshot accessibility hierarchy for app with pid 1429
2020-06-02 12:51:32.065289+0800 XCTestWDUITests-Runner[1424:625693] XCTestWDSetup->start fastmonkey<-XCTestWDSetup
t = 68.76s Find the Any
t = 68.77s Snapshot accessibility hierarchy for app with pid 1429
t = 68.79s Find: Descendants matching type Any
t = 68.79s Find: Element at index 0
t = 68.80s Find the Application 'com.HuaXiaBank.HuaCard'
t = 68.80s Snapshot accessibility hierarchy for app with pid 1429
catching internal failure: Failure fetching attributes for Device system-wide element: Error Domain=XCTDaemonErrorDomain Code=39 "Deprecated API. Call _XCT_fetchAttributes:forElement:reply: instead." UserInfo={NSLocalizedDescription=Deprecated API. Call _XCT_fetchAttributes:forElement:reply: instead.} in file: /Users/chenrui/Desktop/testProgramm/Fastmonkey/Fastmonkey/XCTestWD-master/XCTestWD/XCTestWDUITests/XCTestWDRunner.swift at line: 38
catching internal failure: Failure to determine system application: (null) in file: /Users/chenrui/Desktop/testProgramm/Fastmonkey/Fastmonkey/XCTestWD-master/XCTestWD/XCTestWDUITests/XCTestWDRunner.swift at line: 38
catching internal failure: Failure fetching attributes for (null): Error Domain=XCTDaemonErrorDomain Code=39 "Deprecated API. Call _XCT_fetchAttributes:forElement:reply: instead." UserInfo={NSLocalizedDescription=Deprecated API. Call _XCT_fetchAttributes:forElement:reply: instead.} in file: /Users/chenrui/Desktop/testProgramm/Fastmonkey/Fastmonkey/XCTestWD-master/XCTestWD/XCTestWDUITests/XCTestWDRunner.swift at line: 38
catching internal failure: Failure getting list of active applications: (null) in file: /Users/chenrui/Desktop/testProgramm/Fastmonkey/Fastmonkey/XCTestWD-master/XCTestWD/XCTestWDUITests/XCTestWDRunner.swift at line: 38
catching internal failure: Failure fetching attributes for Device system-wide element: Error Domain=XCTDaemonErrorDomain Code=39 "Deprecated API. Call _XCT_fetchAttributes:forElement:reply: instead." UserInfo={NSLocalizedDescription=Deprecated API. Call _XCT_fetchAttributes:forElement:reply: instead.} in file: /Users/chenrui/Desktop/testProgramm/Fastmonkey/Fastmonkey/XCTestWD-master/XCTestWD/XCTestWDUITests/XCTestWDRunner.swift at line: 38
catching internal failure: Failure to determine system application: (null) in file: /Users/chenrui/Desktop/testProgramm/Fastmonkey/Fastmonkey/XCTestWD-master/XCTestWD/XCTestWDUITests/XCTestWDRunner.swift at line: 38
2020-06-02 12:51:32.127845+0800 XCTestWDUITests-Runner[1424:625693] *** Assertion failure in -[XCUIApplicationMonitor_iOS applicationProcessWithPID:], /Library/Caches/com.apple.xbs/Sources/XCTest_iOS/XCTest-14460.20/Sources/UITesting/Applications/XCUIApplicationMonitor.m:227
t = 68.83s Assertion Failure: XCTestWDRunner.swift:38: failed: caught "NSInternalInconsistencyException", "Invalid pid 0"
(
0 CoreFoundation 0x00000001a8a807a8 50CF3336-313F-3A7D-9048-CB1ED8EC3368 + 1222568
1 libobjc.A.dylib 0x00000001a87a2bcc objc_exception_throw + 56
2 CoreFoundation 0x00000001a898382c 50CF3336-313F-3A7D-9048-CB1ED8EC3368 + 186412
3 Foundation 0x00000001a8dbb16c C82F8A4F-3D0F-33DB-8D40-C1E8BEF27E56 + 553324
4 XCTest 0x0000000102a56660 -[XCUIApplicationMonitor applicationProcessWithPID:] + 372
5 XCTest 0x0000000102a55bfc -[XCUIApplicationMonitor_iOS monitoredApplicationWithProcessIdentifier:] + 48
6 XCTest 0x0000000102aafc08 +[XCUIApplication applicationWithPID:] + 64
7 XCTestWD 0x0000000103caf07c +[XCTestWDApplication createByPID:] + 160
8 XCTestWD 0x0000000103caeef8 +[XCTestWDApplication activeApplication] + 368
9 XCTestWD 0x0000000103cf558c $S8XCTestWD0A9WDSessionC17activeApplicationSo15XCUIApplicationCSgyFZ + 56
10 XCTestWD 0x0000000103d00690 $S8XCTestWD0A18WDFindElementUtilsC9getAppPids5Int32VyFZ + 52
11 XCTestWD 0x0000000103cb0db4 $S8XCTestWD6MonkeyC4seed5frameACs6UInt32V_So6CGRectVtcfc + 980
12 XCTestWD 0x0000000103cb08b8 $S8XCTestWD6MonkeyC5frameACSo6CGRectV_tcfc + 684
13 XCTestWD 0x0000000103cb05fc $S8XCTestWD6MonkeyC5frameACSo6CGRectV_tcfC + 80
14 XCTestWD 0x0000000103d01ae4 $S8XCTestWD0A8WDMonkeyC11startMonkeySiyF + 2104
15 XCTestWDUITests 0x0000000102eea530 $S15XCTestWDUITests14XCTextWDRunnerC10testRunneryyF + 224
16 XCTestWDUITests 0x0000000102eea5a4 $S15XCTestWDUITests14XCTextWDRunnerC10testRunneryyFTo + 40
17 CoreFoundation 0x00000001a8a86970 50CF3336-313F-3A7D-9048-CB1ED8EC3368 + 1247600
18 CoreFoundation 0x00000001a8957bb0 50CF3336-313F-3A7D-9048-CB1ED8EC3368 + 7088
19 XCTest 0x0000000102a7a3ec __24-[XCTestCase invokeTest]_block_invoke_2.202 + 68
20 XCTest 0x0000000102ae33f8 -[XCTMemoryChecker _assertInvalidObjectsDeallocatedAfterScope:] + 68
21 XCTest 0x0000000102a82c70 -[XCTestCase assertInvalidObjectsDeallocatedAfterScope:] + 112
22 XCTest 0x0000000102a7a374 __24-[XCTestCase invokeTest]_block_invoke.196 + 196
23 XCTest 0x0000000102acf068 -[XCTestCase(Failures) performFailableBlock:testCaseRun:shouldInterruptTest:] + 64
24 XCTest 0x0000000102acef80 -[XCTestCase(Failures) _performTurningExceptionsIntoFailuresInterruptAfterHandling:block:] + 108
25 XCTest 0x0000000102a79fe8 __24-[XCTestCase invokeTest]_block_invoke + 812
26 XCTest 0x0000000102ad4bf0 -[XCUITestContext performInScope:] + 264
27 XCTest 0x0000000102a79bf4 -[XCTestCase testContextPerformInScope:] + 100
28 XCTest 0x0000000102a79ca8 -[XCTestCase invokeTest] + 140
29 XCTest 0x0000000102a7b84c __26-[XCTestCase performTest:]_block_invoke_2 + 44
30 XCTest 0x0000000102acf068 -[XCTestCase(Failures) performFailableBlock:testCaseRun:shouldInterruptTest:] + 64
31 XCTest 0x0000000102acef80 -[XCTestCase(Failures) _performTurningExceptionsIntoFailuresInterruptAfterHandling:block:] + 108
32 XCTest 0x0000000102a7b764 __26-[XCTestCase performTest:]_block_invoke.341 + 96
33 XCTest 0x0000000102adf434 +[XCTContext runInContextForTestCase:block:] + 216
34 XCTest 0x0000000102a7af00 -[XCTestCase performTest:] + 648
35 XCTest 0x0000000102abc1ec -[XCTest runTest] + 60
36 XCTest 0x0000000102a76344 __27-[XCTestSuite performTest:]_block_invoke + 296
37 XCTest 0x0000000102a75c44 -[XCTestSuite _performProtectedSectionForTest:testSection:] + 68
38 XCTest 0x0000000102a75edc -[XCTestSuite performTest:] + 272
39 XCTest 0x0000000102abc1ec -[XCTest runTest] + 60
40 XCTest 0x0000000102a76344 __27-[XCTestSuite performTest:]_block_invoke + 296
41 XCTest 0x0000000102a75c44 -[XCTestSuite _performProtectedSectionForTest:testSection:] + 68
42 XCTest 0x0000000102a75edc -[XCTestSuite performTest:] + 272
43 XCTest 0x0000000102abc1ec -[XCTest runTest] + 60
44 XCTest 0x0000000102a76344 __27-[XCTestSuite performTest:]_block_invoke + 296
45 XCTest 0x0000000102a75c44 -[XCTestSuite _performProtectedSectionForTest:testSection:] + 68
46 XCTest 0x0000000102a75edc -[XCTestSuite performTest:] + 272
47 XCTest 0x0000000102abc1ec -[XCTest runTest] + 60
48 XCTest 0x0000000102aed9f8 __44-[XCTTestRunSession runTestsAndReturnError:]_block_invoke + 176
49 XCTest 0x0000000102aedb28 __44-[XCTTestRunSession runTestsAndReturnError:]_block_invoke.80 + 60
50 XCTest 0x0000000102a8dc70 -[XCTestObservationCenter _observeTestExecutionForBlock:] + 516
51 XCTest 0x0000000102aed778 -[XCTTestRunSession runTestsAndReturnError:] + 612
52 XCTest 0x0000000102a5ae24 -[XCTestDriver runTestsAndReturnError:] + 416
53 XCTest 0x0000000102adbc50 _XCTestMain + 1436
54 XCTestWDUITests-Runner 0x00000001026bfb18 -[_XCTRunnerAppDelegate applicationWillResignActive:] + 0
55 XCTestWDUITests-Runner 0x00000001026bfa20 _XCTRunnerRunTests + 0
56 CoreFoundation 0x00000001a89fea4c 50CF3336-313F-3A7D-9048-CB1ED8EC3368 + 690764
57 CoreFoundation 0x00000001a89fe1d8 50CF3336-313F-3A7D-9048-CB1ED8EC3368 + 688600
58 CoreFoundation 0x00000001a89f933c 50CF3336-313F-3A7D-9048-CB1ED8EC3368 + 668476
59 CoreFoundation 0x00000001a89f8ce8 CFRunLoopRunSpecific + 424
60 GraphicsServices 0x00000001b2b4338c GSEventRunModal + 160
61 UIKitCore 0x00000001acb27444 UIApplicationMain + 1932
62 XCTestWDUITests-Runner 0x00000001026bfcf8 main + 192
63 libdyld.dylib 0x00000001a88808f0 90BD401C-9E8F-354E-A74F-D4C152DEB1D8 + 6384
)
t = 68.86s Tear Down
t = 68.86s Pressing Home button
t = 68.90s Pressing Home button
Test Case '-[XCTestWDUITests.XCTextWDRunner testRunner]' failed (68.921 seconds).
Test Suite 'XCTextWDRunner' failed at 2020-06-02 12:51:32.225.
Executed 1 test, with 1 failure (1 unexpected) in 68.921 (68.924) seconds
Test Suite 'XCTestWDUITests.xctest' failed at 2020-06-02 12:51:32.226.
Executed 1 test, with 1 failure (1 unexpected) in 68.921 (68.926) seconds
Test Suite 'All tests' failed at 2020-06-02 12:51:32.227.
Executed 1 test, with 1 failure (1 unexpected) in 68.921 (68.934) seconds
相關文章
- [解決] Goland 開啟後直接崩潰GoLand
- win10系統驅動崩潰怎麼辦_win10系統驅動經常崩潰解決方法Win10
- 誤升級GLIBC導致系統崩潰之後
- 成都、貴州核酸檢測系統“崩潰”背後的技術原因
- win10系統崩潰藍屏什麼原因 win10系統出現崩潰藍屏如何修復Win10
- 怎麼樣把mysqld壓測到崩潰重啟?什麼情況下mysqld崩潰重啟?MySql
- WWDC 2018:理解崩潰以及崩潰日誌
- win10系統下AMD驅動程式崩潰了怎麼解決Win10
- 崩潰的一天,西安一碼通崩潰背後的技術問題。
- win10系統崩潰藍色畫面什麼原因 win10系統出現崩潰藍色畫面如何修復Win10
- win10 qq影片崩潰怎麼修復_win10系統qq影片老是崩潰解決方法Win10
- 益普索:2022年崩潰系統情緒調查
- win10系統下資源管理器頻繁崩潰重啟如何解決Win10
- APP防崩潰APP
- 崩潰日記
- win10系統用一會就崩潰如何解決Win10
- qq遊戲崩潰w10解決方法_w10系統玩qq遊戲老崩潰如何修復遊戲
- win10 qq視訊崩潰怎麼修復_win10系統qq視訊老是崩潰解決方法Win10
- 微軟修復了導致 Outlook 啟動時崩潰的問題微軟
- win10系統firefox多開崩潰怎麼修復_win10 firefox多開總是崩潰解決方法Win10Firefox
- 記一次 .NET某新能源檢測系統 崩潰分析
- k8s克隆節點引起的系統崩潰問題K8S
- iOS Crash不崩潰iOS
- app 崩潰的原因APP
- 電腦系統崩潰怎麼修復 修復電腦系統的三種方法
- 華為手機使用 appium 截圖後,app 崩潰APP
- 執行緒崩潰為什麼不會導致 JVM 崩潰執行緒JVM
- 生產級部署 Python 指令碼,崩潰可自啟!Python指令碼
- Linux中程式崩潰及重啟的原因詳解!Linux
- 記一次 .NET 某新能源材料檢測系統 崩潰分析
- 案例解析:執行緒池使用不當導致的系統崩潰執行緒
- Facebook是如何防止訊息系統在新年前夕發生崩潰?
- 記一次 .NET 某企業 ERP網站系統 崩潰分析網站
- 記一次 .NET 某教育系統API 異常崩潰分析API
- 檔案系統(七):檔案系統崩潰一致性、方法、原理與侷限
- 令人崩潰的自動駕駛:看完這個影片後,我不敢「開」特斯拉了自動駕駛
- node啟動程式-清理由於崩潰導致的沒有關掉的程式
- SOLIDWORKS培訓教程 | SW崩潰後如何恢復檔案?Solid