Enable strict concurrency checking in the Swift Package in a PR and ensure that we don't have any warnings remaining in the packages as we develop new features or fix bugs from now.
The corresponding PR should fix all related warnings when enabling strict concurrency checking.
Additional context
We should consider adding SWIFT_TREAT_WARNINGS_AS_ERRORS = YES to our general workflows to ensure all warnings are flagged as errors during our CI setup.
Code of Conduct
[X] I agree to follow this project's Code of Conduct and Contributing Guidelines
Problem
With Swift 6 approaching in a few months and nightly builds already being available we should ensure that all our packages are working well with all Swift concurrency checks.
Solution
Enable strict concurrency checking in the Swift Package in a PR and ensure that we don't have any warnings remaining in the packages as we develop new features or fix bugs from now.
The UI Testing App target should also enable Enable strict concurrency checking.
The corresponding PR should fix all related warnings when enabling strict concurrency checking.
Additional context
We should consider adding
SWIFT_TREAT_WARNINGS_AS_ERRORS = YESto our general workflows to ensure all warnings are flagged as errors during our CI setup.Code of Conduct