xamarin/Xamarin.Forms

[Bug] iPhone 11 Pro throws NSInternalInconsistencyException with reason No view controller managing revealed view

Open

#9,347 建立於 2020年1月28日

在 GitHub 查看
 (8 留言) (0 反應) (0 負責人)C# (5,644 star) (1,926 fork)batch import
a/listviewhas-stacktracehelp wantedi/highp/iOS 🍎s/unverifiedt/bug :bug:up-for-grabs

描述

Description

A crash was reported when accessing a view with a ListView element.

  • Platform Target Frameworks:
    • iOS: SDK 12.8
  • Affected Devices: iPhone 11 Pro, version 13.0. Testing reports that it did not happen on XR running iOS 12.0 or iPhone 11 Pro Max running iOS 13.1.3.
  • XF version: 4.4.0.991265

SIGABRT: Objective-C exception thrown. Name: NSInternalInconsistencyException Reason: No view controller managing revealed view <Xamarin_Forms_Platform_iOS_Platform_DefaultRenderer: 0x12bb25170; frame = (0 43.6667; 375 566); autoresize = LM+W+RM+TM+H+BM; layer = <CALayer: 0x2814f1ce0>> Native stack trace: 0 CoreFoundation 0x00000001bd029560 2A356815-C9F4-3364-9AAC-B56FC2A4DD20 + 1254752 1 libobjc.A.dylib 0x00000001bcd440c8 objc_exception_throw + 60 2 CoreFoundation 0x00000001bcf26330 2A356815-C9F4-3364-9AAC-B56FC2A4DD20 + 193328 3 Foundation 0x00000001bd366368 027A1168-54B3-30BA-82E5-640520D2E2CB + 570216 4 UIKitCore 0x00000001c09f4bd8 DF8357C2-E01B-3003-98A4-020E09405CA8 + 3677144 5 UIKitCore 0x00000001c09ff548 DF8357C2-E01B-3003-98A4-020E09405CA8 + 3720520 6 UIKitCore 0x00000001c0a00a18 DF8357C2-E01B-3003-98A4-020E09405CA8 + 3725848 7 UIKitCore 0x00000001c0a0063c DF8357C2-E01B-3003-98A4-020E09405CA8 + 3724860 8 UIKitCore 0x00000001c09fc574 DF8357C2-E01B-3003-98A4-020E09405CA8 + 3708276 9 UIKitCore 0x00000001c15335b0 DF8357C2-E01B-3003-98A4-020E09405CA8 + 15467952 10 libobjc.A.dylib 0x00000001bcd3faf0 E2A0B9FF-CD66-3DB3-9D91-F7A5A41FB02D + 6896 11 QuartzCore 0x00000001c3ad9c0c CCC9DE43-BF6E-3736-81EC-6A38611EF775 + 1395724 12 QuartzCore 0x00000001c3ad9f14 CCC9DE43-BF6E-3736-81EC-6A38611EF775 + 1396500 13 QuartzCore 0x00000001c3aed3fc CCC9DE43-BF6E-3736-81EC-6A38611EF775 + 1475580 14 QuartzCore 0x00000001c3a32184 CCC9DE43-BF6E-3736-81EC-6A38611EF775 + 708996 15 QuartzCore 0x00000001c3a5d228 CCC9DE43-BF6E-3736-81EC-6A38611EF775 + 885288 16 QuartzCore 0x00000001c3996c70 CCC9DE43-BF6E-3736-81EC-6A38611EF775 + 72816 17 QuartzCore 0x00000001c3a65004 CCC9DE43-BF6E-3736-81EC-6A38611EF775 + 917508 18 CoreFoundation 0x00000001bcf7a890 2A356815-C9F4-3364-9AAC-B56FC2A4DD20 + 538768 19 CoreFoundation 0x00000001bcfa51fc 2A356815-C9F4-3364-9AAC-B56FC2A4DD20 + 713212 20 CoreFoundation 0x00000001bcfa48c8 2A356815-C9F4-3364-9AAC-B56FC2A4DD20 + 710856 21 CoreFoundation 0x00000001bcf9f500 2A356815-C9F4-3364-9AAC-B56FC2A4DD20 + 689408 22 CoreFoundation 0x00000001bcf9e978 CFRunLoopRunSpecific + 480 23 GraphicsServices 0x00000001c70ce534 GSEventRunModal + 108 24 UIKitCore 0x00000001c1090f0c UIApplicationMain + 1940 25 NEXTConnect 0x00000001058be6b4 _ZN7plcrash2MS5async24dwarf_cfa_state_iteratorIyxE4nextEPjPNS1_28plcrash_dwarf_cfa_reg_rule_tEPy + 13607824 26 NEXTConnect 0x00000001058ed004 _ZN7plcrash2MS5async24dwarf_cfa_state_iteratorIyxE4nextEPjPNS1_28plcrash_dwarf_cfa_reg_rule_tEPy + 13798624 27 NEXTConnect 0x00000001065ed7a8 _ZN7plcrash2MS5async24dwarf_cfa_state_iteratorIyxE4nextEPjPNS1_28plcrash_dwarf_cfa_reg_rule_tEPy + 27432068 28 NEXTConnect 0x0000000106690bc0 _ZN7plcrash2MS5async24dwarf_cfa_state_iteratorIyxE4nextEPjPNS1_28plcrash_dwarf_cfa_reg_rule_tEPy + 28100764 29 NEXTConnect 0x0000000106696dc0 _ZN7plcrash2MS5async24dwarf_cfa_state_iteratorIyxE4nextEPjPNS1_28plcrash_dwarf_cfa_reg_rule_tEPy + 28125852 30 NEXTConnect 0x00000001065cc22c _ZN7plcrash2MS5async24dwarf_cfa_state_iteratorIyxE4nextEPjPNS1_28plcrash_dwarf_cfa_reg_rule_tEPy + 27295496 31 NEXTConnect 0x000000010675fc4c xamarin_release_block_on_main_thread + 24392 32 NEXTConnect 0x0000000104c2ace0 _ZN7plcrash2MS5async24dwarf_cfa_state_iteratorIyxE4nextEPjPNS1_28plcrash_dwarf_cfa_reg_rule_tEPy + 420284 33 libdyld.dylib 0x00000001bce1ef04 B4D308AE-C33B-33ED-A2D3-D362FFC4327D + 3844

Not really sure of the cause, but it's pointing to xamarin code (I think). If more information is needed, I can dig further.

貢獻者指南

技術棧
csharpios
領域
mobile
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
4
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
3-5 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
C# and Xamarin.Forms experienceiOS development basicsKnowledge of UIViewController lifecycle
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
20
研究方向
Investigate the crash by analyzing the stack trace in the Xamarin.Forms source code, focusing on the Xamarin Forms Platform iOS Platform DefaultRenderer class. Look at how view controllers are managed in Xamarin.Forms for iOS, especially for the iPhone 11 Pro on iOS 13.0. Check if there are any known issues with ListView and view controller containment. Reproduce the issue on a simulator or device with the same configuration to identify the root cause.