[ci-scan] Recurring: VerifyCursorPositionWhenSelectionLengthSetValue causes app crash on Android API 30 (maui-pr-uitests)

[github-actions]

Summary

VerifyCursorPositionWhenSelectionLengthSetValue causes the test app to crash on Android API 30 emulator, producing "The app was expected to be running still, investigate as possible crash" in the TearDown phase.

Build Information

• Pipeline: maui-pr-uitests (definition 313)
• Build: 1484478
• Build ID: 1484478
• Branch: main
• First seen: 2026-06-23 (build 1476735)
• Occurrences: 2 in last 10 builds (1476735 on 2026-06-23, 1484478 on 2026-06-27)

Affected Legs

• Android — Controls (API 30) Entry → Run DeviceTests Android (Helix, API 30 emulator)

Error Message

Failed VerifyCursorPositionWhenSelectionLengthSetValue [27 s]
  Error Message:
   The app was expected to be running still, investigate as possible crash
TearDown : The app was expected to be running still, investigate as possible crash
  Stack Trace:
     at UITest.Appium.NUnit.UITestBase.UITestBaseTearDown() in /_/src/TestUtils/src/UITest.NUnit/UITestBase.cs:line 159
   at UITest.Appium.NUnit.UITestBase.TestTearDown() in /_/src/TestUtils/src/UITest.NUnit/UITestBase.cs:line 45

Recommended Action

1. Find the test in src/Controls/tests/TestCases.Shared.Tests/ (search for VerifyCursorPositionWhenSelectionLengthSetValue).
2. Run the test locally on an Android API 30 emulator and capture a crash log or ADB logcat to identify the crash type (ANR, native crash, OutOfMemoryError, etc.).
3. Investigate whether Entry.SelectionLength interaction with the soft keyboard or IME on Android API 30 causes a platform crash.
4. If this is an API 30-specific regression, consider adding [ActiveIssue] with the TestPlatforms.Android annotation as a short-term workaround.

Generated by CI Failure Scanner · claude-sonnet-4.6

Generated by CI Failure Scanner · 5.7K AIC · ⌖ 13.8 AIC · ⊞ 36.2K · ◷

[PureWeen]

Closing this scanner issue as stale/non-reproducing after exact-test review. VerifyCursorPositionWhenSelectionLengthSetValue passed on the affected Android API 30 leg across five complete main UI builds from 1533309 through 1544324, with no matching app-crash signature. No root-cause fix is claimed.