Update API level in UI tests critical#4638
Merged
alexander-alderman-webb merged 1 commit intomainfrom Aug 14, 2025
Merged
Conversation
Contributor
Performance metrics 🚀
|
stefanosiano
approved these changes
Aug 14, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
📜 Description
#skip-changelog
Testing against a newer Android API-level in CI and dropping the oldest one. At the time the UI tests were added the most recent versions were selected, but since then new versions have been released.
💡 Motivation and Context
We have experienced issues with the API level 30 in the UI tests critical action, resulting in our CI hanging. See the recent cancelled runs: https://github.com/getsentry/sentry-java/actions?query=is%3Acancelled
See related thread: ReactiveCircus/android-emulator-runner#385
💚 How did you test it?
📝 Checklist
sendDefaultPIIis enabled.🔮 Next steps