Summary
EditorRuntimeTextAlignmentChanged (Issue10987) fails intermittently with NoSuchElementException on the iOS latest simulator in maui-pr-uitests. The test cannot locate an element on the page — the app may not have fully rendered before the assertion fires.
Build Information
- Pipeline: maui-pr-uitests
- Build: 1491409
- Build ID: 1491409
- Branch: net11.0
- First seen: 2026-07-01 (build 1489335)
- Occurrences: 2 in last 6 builds (1491409, 1489335)
Affected Legs
Controls (vlatest) Editor,Effects,Essentials,FlyoutPage,Focus,Fonts,Frame,Gestures,GraphicsView — iOS simulator (vlatest, CoreCLR)
Error Message
Failed EditorRuntimeTextAlignmentChanged [4–6 s]
Error Message:
OpenQA.Selenium.NoSuchElementException : An element could not be located on the page
using the given search parameters.
For documentation on this error, please visit:
(www.selenium.dev/redacted)
Stack Trace:
at OpenQA.Selenium.WebDriver.ExecuteAsync(String driverCommandToExecute, ...)
at Microsoft.Maui.TestCases.Tests.Issues.Issue10987.EditorRuntimeTextAlignmentChanged()
in /_/src/Controls/tests/TestCases.Shared.Tests/Tests/Issues/Issue10987.cs:line 34
Recommended Action
- Open
src/Controls/tests/TestCases.Shared.Tests/Tests/Issues/Issue10987.cs at line 34 and check what element is being located.
- The
NoSuchElementException suggests the test navigates to a page but the target UI element is not yet present before the implicit Appium timeout. Add an explicit WaitForElement call before the assertion to handle async rendering on iOS.
- Check if recent changes to the iOS
Editor handler (src/Controls/src/Core/Handlers/Editor/) or to src/Controls/tests/TestCases.HostApp/Issues/Issue10987.xaml changed the element hierarchy or automation IDs.
- The test passes intermittently (e.g., it passes in build 1493717 on the same leg) — this confirms a timing/race condition rather than a permanent regression.
Generated by CI Failure Scanner (net11.0)
Generated by CI Failure Scanner (net11.0) · 3.3K AIC · ⌖ 24.9 AIC · ⊞ 36.2K · ◷
Summary
EditorRuntimeTextAlignmentChanged(Issue10987) fails intermittently withNoSuchElementExceptionon the iOS latest simulator inmaui-pr-uitests. The test cannot locate an element on the page — the app may not have fully rendered before the assertion fires.Build Information
Affected Legs
Controls (vlatest) Editor,Effects,Essentials,FlyoutPage,Focus,Fonts,Frame,Gestures,GraphicsView— iOS simulator (vlatest, CoreCLR)Error Message
Recommended Action
src/Controls/tests/TestCases.Shared.Tests/Tests/Issues/Issue10987.csat line 34 and check what element is being located.NoSuchElementExceptionsuggests the test navigates to a page but the target UI element is not yet present before the implicit Appium timeout. Add an explicitWaitForElementcall before the assertion to handle async rendering on iOS.Editorhandler (src/Controls/src/Core/Handlers/Editor/) or tosrc/Controls/tests/TestCases.HostApp/Issues/Issue10987.xamlchanged the element hierarchy or automation IDs.