Flaky Test Report (automated)
Test: MonoTouchFixtures.CategoryTest.NavigationControllerOverride
Platform: iOS (simulator, Debug)
Category: Flaky
Period: June 29, 2026
Occurrence Summary
Total: Failed in 1 build; rerun (attempt 2) was triggered, confirming suspected flakiness.
Error Details
ObjCRuntime.RuntimeException : Failed to lookup the required marshalling information.
Additional information:
Selector: xamarinApplySelector
Type: __MonoMac_NSAsyncActionDispatcher
Code: 8034
Error: True
----> ObjCRuntime.RuntimeException : Failed to get the 'this' instance in a method call to Foundation.NSAsyncActionDispatcher.Apply.
Code: 8035
Error: True
----> ObjCRuntime.RuntimeException : Failed to marshal the Objective-C object 0x128759080 (type: __MonoMac_NSAsyncActionDispatcher). Could not find an existing managed instance for this object, nor was it possible to create a new managed instance (because the type 'Foundation.NSAsyncActionDispatcher' does not have a constructor that takes one NativeHandle argument).
Code: 8027
Error: True
Stack trace:
at ObjCRuntime.Runtime.RethrowManagedException(IntPtr exception_gchandle)
at ObjCRuntime.Runtime.rethrow_managed_exception(...)
at Foundation.NSRunLoop.RunUntil(NSDate date)
at AppDelegate.PresentModalViewController(UIViewController vc, Double duration) in SceneDelegate.cs:line 40
at MonoTouchFixtures.CategoryTest.NavigationControllerOverride()
Analysis
This is a GC race condition: NSAsyncActionDispatcher gets garbage-collected while native code still holds a reference to it. When NSRunLoop.RunUntil() delivers the async callback via xamarinApplySelector, the managed instance is gone and cannot be recreated because Foundation.NSAsyncActionDispatcher lacks a NativeHandle constructor.
The test itself (CategoryTest.NavigationControllerOverride) is about Objective-C category overrides on UINavigationController. The marshalling failure in NSAsyncActionDispatcher is a side effect — an unrelated async dispatch races with the GC during the modal presentation loop.
Classification
This failure was identified as flaky because:
This issue was automatically generated by CI post-mortem analysis.
Flaky Test Report (automated)
Test:
MonoTouchFixtures.CategoryTest.NavigationControllerOverridePlatform: iOS (simulator, Debug)
Category: Flaky
Period: June 29, 2026
Occurrence Summary
Total: Failed in 1 build; rerun (attempt 2) was triggered, confirming suspected flakiness.
Error Details
Stack trace:
Analysis
This is a GC race condition:
NSAsyncActionDispatchergets garbage-collected while native code still holds a reference to it. WhenNSRunLoop.RunUntil()delivers the async callback viaxamarinApplySelector, the managed instance is gone and cannot be recreated becauseFoundation.NSAsyncActionDispatcherlacks aNativeHandleconstructor.The test itself (
CategoryTest.NavigationControllerOverride) is about Objective-C category overrides onUINavigationController. The marshalling failure inNSAsyncActionDispatcheris a side effect — an unrelated async dispatch races with the GC during the modal presentation loop.Classification
This failure was identified as flaky because:
tools/common/ErrorHelper.tools.cs,tools/common/error.cs) — completely unrelated to runtime marshallingThis issue was automatically generated by CI post-mortem analysis.