We have encountered the same issue in our app. All of the recent crashes are coming from iOS 14.6.0 (18F72) and are exclusive to iPads. Seems like the issue originates from the WebView controller that presents something with a table (I suspect the ActionSheet view on the select component) log.crash Fatal Exception: NSInternalInconsistencyException UITableView dataSource is not set Fatal Exception: NSInternalInconsistencyException 0 CoreFoundation 0x1a1321298 __exceptionPreprocess 1 libobjc.A.dylib 0x1b507b480 objc_exception_throw 2 CoreFoundation 0x1a122ecc8 -[CFPrefsSearchListSource addManagedSourceForIdentifier:user:] 3 Foundation 0x1a2566128 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] 4 UIKitCore 0x1a3dd9c9c -[UITableView _createPreparedCellForGlobalRow:withIndexPath:willDisplay:] 5 UIKitCore 0x1a3dd9e9c -[UITableView _createPreparedCellForRowAtIndexPath:willDisplay:] 6 UIKitCore 0x1a3de5208 -[UITableView _heightForRowAtIndexPath:] 7 UIKitCore 0x1a3df7864 -[UISectionRowData heightForRow:inSection:canGuess:] 8 UIKitCore 0x1a3dfc738 -[UITableViewRowData heightForRow:inSection:canGuess:adjustForReorderedRow:] 9 UIKitCore 0x1a3dfdd5c -[UITableViewRowData rectForRow:inSection:heightCanBeGuessed:] 10 UIKitCore 0x1a3db9428 -[UITableView _rectForRowAtIndexPath:usingPresentationValues:] 11 UIKitCore 0x1a3dbaa80 -[UITableView _contentOffsetForScrollingToRowAtIndexPath:atScrollPosition:usingPresentationValues:] 12 UIKitCore 0x1a3dbb6e8 -[UITableView _scrollToRowAtIndexPath:atScrollPosition:animated:usingPresentationValues:] 13 UIKitCore 0x1a3dbb554 -[UITableView scrollToRowAtIndexPath:atScrollPosition:animated:] 14 WebKit 0x1ad108d54 -[WKSelectTableViewController viewWillAppear:] 15 UIKitCore 0x1a3504a64 -[UIViewController _setViewAppearState:isAnimating:] 16 UIKitCore 0x1a35051e8 -[UIViewController __viewWillAppear:] 17 UIKitCore 0x1a33f27bc __56-[UIPresentationController runTransitionForCurrentState]_block_invoke.466 18 UIKitCore 0x1a4064cfc -[_UIAfterCACommitBlock run] 19 UIKitCore 0x1a3bd47dc _runAfterCACommitDeferredBlocks 20 UIKitCore 0x1a3bc3ca8 _cleanUpAfterCAFlushAndRunDeferredBlocks 21 UIKitCore 0x1a3bf4ff8 _afterCACommitHandler 22 CoreFoundation 0x1a129f588 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ 23 CoreFoundation 0x1a1299bb8 __CFRunLoopDoObservers 24 CoreFoundation 0x1a129a154 __CFRunLoopRun 25 CoreFoundation 0x1a1299818 CFRunLoopRunSpecific 26 GraphicsServices 0x1b799f570 GSEventRunModal 27 UIKitCore 0x1a3bc50e8 -[UIApplication _run] 28 UIKitCore 0x1a3bca664 UIApplicationMain 29 [Redacted] 0x10060f764 main + 11 (AppDelegate.swift:11) 30 libdyld.dylib 0x1a0f78140 start Would appreciate any help with this issue, Quinn!

Same as @McCarron here: The back navigation title feature is introduced exactly to give an opportunity to specify a special case of the Back title where the title of the View won't be feasible/optimal. Why then limiting the navigation menu to only back titles? There are a lot of use cases where the Back navigation title works the best in the context of the screen, but doesn't work at all outside of it in some sort of the vertical stack list with no context. That would be much better to either give an opportunity to override it the same way we a given with the .backBarButtonItem