fix(android_alarm_manager_plus): Fix integration test #2115
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
The integration test for the lower Android API level fails since it was recently changed from 21 to 22.
The test already failed in the PR changing the version, and since then in all workflow runs using the new API level. In a current PR, the test failed seven times in a row. Unless we find the actual cause, it makes sense to revert the API level change.
This PR changes the version to the one that worked fine before.
In the future, I would suggest only merging PRs with successful tests (if they worked before), so we limit regressions on
main
and fix the issue when it arises, which is easier than finding the cause afterwards and having issues in unrelated PRs.This change was already included in #2112 to check if it helps. Suggestion is to first merge this one, rebase, and merge the other one.
Checklist
CHANGELOG.md
nor the plugin version inpubspec.yaml
files.flutter analyze
) does not report any problems on my PR.Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?
!
in the title as explained in Conventional Commits).