iPad app terminated by watchdog (0x8BADF00D) during navigation transition — only with AssistiveTouch enabled (iPadOS 26)

Question

Created 1d

Replies 1

Boosts 0

Participants 2

Our app is being killed by the watchdog on iPadOS 26 (iPad Pro 11, 3rd gen) when navigating between tabs after using search. The crash only occurs when AssistiveTouch is enabled — disabling it prevents the issue entirely.

The crash stack shows the main thread blocked in CoreUI vector glyph rasterization (CUINamedVectorGlyph _layerNamesForRenderingMode:inRendition:) triggered during a UINavigationController transition while the keyboard is being dismissed:

UINavigationController _startCustomTransition → UIKeyboardSceneDelegate _restoreInputViewsWithId → UITextField resignFirstResponder → SwiftUI ViewGraphRootValueUpdater.render → UIButton layoutSubviews → UIImageView _setImage → CUINamedVectorGlyph _layerNamesForRenderingMode:inRendition:

The termination reason:

FRONTBOARD domain:10 code:0x8BADF00D "Failed to terminate gracefully after 5.0s" WatchdogEvent: process-exit WatchdogVisibility: Foreground

Key observations:

Only reproduces with AssistiveTouch enabled
iPad Pro 11 (3rd gen), iPadOS 26
Our code is not on the crashing thread — it's entirely UIKit/CoreUI/SwiftUI framework code
Similar to issues reported in thread/808808 (https://developer.apple.com/forums/thread/808808) and dotnet/maui#32365 (https://github.com/dotnet/maui/issues/32365)

Is this a known issue with AssistiveTouch + UINavigationController transitions on iPadOS 26? Is there a recommended workaround?

Answer 1

Frameworks Engineer OP

Apple

7h

The code path your reporting may not go through your code, but it may have input from you that is causing the issue, although its impossible to tell if its one of your symbols or a system symbol that is being rendered from this report.

That said, the best way to ensure that someone can act on this issue is to use the Feedback Assistant https://feedbackassistant.apple.com/ to report the issue formally.