App Minimum and Target SDK Version

Oct 13, 2025 by magicalceylontours.com 62 views

Introduction

The RichSuggestBox DeleteTokens test has been failing intermittently in our Continuous Integration (CI) environment, causing issues with our build process. This test is crucial for ensuring the stability and reliability of our RichSuggestBox component. In this article, we will delve into the details of the issue, explore possible causes, and discuss potential solutions.

Describe the Bug

The test in question is Test_RichSuggestBox_DeleteTokens (@Token1,#Token2), which is failing intermittently in our CI environment. The error message indicates that the expected token count is 2, but the actual token count is 1. This discrepancy is causing the test to fail.

Failed Test_RichSuggestBox_DeleteTokens (@Token1,#Token2) [108 ms]
  Error Message:
   Assert.AreEqual failed. Expected:<2>. Actual:<1>. Unexpected token count after adding.
  Stack Trace:
     at RichSuggestBoxExperiment.Tests.Test_RichSuggestBox.<>c__DisplayClass2_0.<<Test_RichSuggestBox_DeleteTokens>b__0>d.MoveNext() in D:\a\Windows\Windows\components\RichSuggestBox\tests\Test_RichSuggestBox.cs:line 143
--- End of stack trace from previous location ---
   at CommunityToolkit.WinUI.DispatcherQueueExtensions.<>c__DisplayClass3_0.<<EnqueueAsync>b__1>d.MoveNext() in /_/components/Extensions/src/Dispatcher/DispatcherQueueExtensions.cs:line 180
--- End of stack trace from previous location ---
   at RichSuggestBoxExperiment.Tests.Test_RichSuggestBox.Test_RichSuggestBox_DeleteTokens(String token1, String token2) in D:\a\Windows\Windows\components\RichSuggestBox\tests\Test_RichSuggestBox.cs:line 133
   at Microsoft.VisualStudio.TestPlatform.MSTestAdapter.PlatformServices.ThreadOperations.ExecuteWithAbortSafety(Action action)

Steps to Reproduce

To reproduce this issue, follow these steps:

Run the CI environment.

Expected Behavior

The expected behavior is that the test should not fail in the CI environment.

Screenshots

No screenshots are available for this issue.

Code Platform

The following platforms are affected by this issue:

WinAppSDK / WinUI 3

Windows Build Number

The following Windows build numbers are affected by this issue:

Windows 10 1809 (Build 17763)
Windows 10 1903 (Build 18362)
Windows 10 1909 (Build 18363)
Windows 10 2004 (Build 19041)
Windows 10 20H2 (Build 19042)
Windows 10 21H1 (Build 19043)
Windows 10 21H2 (Build 19044)
Windows 10 22H2 (Build 19045)
Windows 11 21H2 (Build 22000)

App Minimum and Target SDK Version

The following app minimum and target SDK versions are affected by this issue:

Windows 10, version 1809 (Build 17763)
Windows 10, version 1903 (Build 18362)
Windows 10, version 1909 (Build 18363)
Windows 10, version 2004 (Build 19041)
Windows 10, version 2104 (Build 20348)
Windows 11, version 22H2 (Build 22000)

Visual Studio Version

No Visual Studio version is specified for this issue.

Visual Studio Build Number

No Visual Studio build number is specified for this issue.

Device Form Factor

No device form factor is specified for this issue.

Additional Context

No additional context is available for this issue.

Help Us Help You

Yes, but only if others can assist.

Possible Causes

Based on the error message and stack trace, it appears that the issue may be related to a race condition or an underlying issue with the platform. The test is failing intermittently, which suggests that the issue may be related to a timing or synchronization problem.

Potential Solutions

To resolve this issue, we can try the following:

Increase the test timeout: We can increase the test timeout to allow the test to complete successfully.
Use a synchronization mechanism: We can use a synchronization mechanism, such as a lock or a semaphore, to ensure that the test is executed in a thread-safe manner.
Fix the underlying platform issue: We can investigate and fix the underlying platform issue that is causing the test to fail.

Conclusion

Q: What is the RichSuggestBox DeleteTokens test?

A: The RichSuggestBox DeleteTokens test is a test case in our RichSuggestBox component that checks the functionality of deleting tokens from the suggest box.

Q: Why is the test failing intermittently?

A: The test is failing intermittently due to a race condition or an underlying issue with the platform. The test is checking the token count after adding, but the actual token count is not matching the expected token count.

Q: What is the expected behavior of the test?

A: The expected behavior of the test is that it should not fail in the CI environment. The test should successfully delete the tokens from the suggest box and verify that the token count is correct.

Q: What are the possible causes of the issue?

A: The possible causes of the issue are:

Race condition: The test is failing due to a race condition, where the test is trying to access the token count before it is updated.
Underlying platform issue: The test is failing due to an underlying issue with the platform, such as a bug in the RichSuggestBox component.

Q: How can we resolve the issue?

A: We can try the following to resolve the issue:

Increase the test timeout: We can increase the test timeout to allow the test to complete successfully.
Use a synchronization mechanism: We can use a synchronization mechanism, such as a lock or a semaphore, to ensure that the test is executed in a thread-safe manner.
Fix the underlying platform issue: We can investigate and fix the underlying platform issue that is causing the test to fail.

Q: What are the affected platforms?

A: The affected platforms are:

WinAppSDK / WinUI 3

Q: What are the affected Windows build numbers?

A: The affected Windows build numbers are:

Windows 10 1809 (Build 17763)
Windows 10 1903 (Build 18362)
Windows 10 1909 (Build 18363)
Windows 10 2004 (Build 19041)
Windows 10 20H2 (Build 19042)
Windows 10 21H1 (Build 19043)
Windows 10 21H2 (Build 19044)
Windows 10 22H2 (Build 19045)
Windows 11 21H2 (Build 22000)

Q: What are the affected app minimum and target SDK versions?

A: The affected app minimum and target SDK versions are:

Windows 10, version 1809 (Build 17763)
Windows 10, version 1903 (Build 18362)
Windows 10, version 1909 (Build 18363)
Windows 10, version 2004 (Build 19041)
Windows 10, version 2104 (Build 20348)
Windows 11, version 22H2 (Build 22000)

Q: Can others assist with resolving the issue?

A: Yes, others can assist with resolving the issue. We are open to suggestions and ideas on how to resolve the issue.