[Android 17] Added Android 17 device to Firebase tests - #193251
Merged
auto-submit[bot] merged 2 commits intoSep 29, 2026
Merged
Conversation
15 of 25 tasks
Contributor
There was a problem hiding this comment.
Code Review
This pull request adds a new physical device configuration for the 'cubs' model to the CI targets in .ci.yaml. However, the specified Android version 37 does not exist yet and is unsupported by Firebase Test Lab, which will cause test failures. It is recommended to update the configuration to use a supported version, such as 34.
6 of 11 tasks
gmackall
approved these changes
Sep 29, 2026
mboetger
approved these changes
Sep 29, 2026
auto-submit Bot
pushed a commit
to flutter/packages
that referenced
this pull request
Sep 29, 2026
flutter/flutter@c5a061b...55b8f88 2026-09-29 jesswon@google.com [Android 17] Added Android 17 device to Firebase tests (flutter/flutter#193251) 2026-09-29 bkonyi@google.com [engine] Fix remaining `unawaited_futures` lints (flutter/flutter#193508) 2026-09-29 chris@bracken.jp shell: Rename first-frame tests AddFirstFrameCallback* (flutter/flutter#193418) 2026-09-28 victorsanniay@gmail.com Enable `unawaited_futures` lint across the Flutter repository (flutter/flutter#193125) 2026-09-28 jesswon@google.com Upgrade flutter/flutter to Roblectric 4.17 (flutter/flutter#193369) 2026-09-28 63228361+krll-kov@users.noreply.github.com [engine] Decode animation frames with alpha after an opaque first frame (flutter/flutter#193113) 2026-09-28 15619084+vashworth@users.noreply.github.com Allow macOS tests to use macOS 15 or 26 (flutter/flutter#193317) 2026-09-28 nshahan@google.com Cleanup DDC SDK build targets (flutter/flutter#193193) If this roll has caused a breakage, revert this CL and set the roller to dry run mode using the controls here: https://autoroll.skia.org/r/flutter-packages Please CC quncheng@google.com,stuartmorgan@google.com on the revert to ensure that a human is aware of the problem. To file a bug in Packages: https://github.com/flutter/flutter/issues/new/choose To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
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.
Added Android 17 device
cubsto Firebase tests. Rangcloud firebase test android models listto check the device exists.Partially Addresses #189518
Pre-launch Checklist
///).If you need help, consider asking for advice on the #hackers-new channel on Discord.
If this change needs to override an active code freeze, provide a comment explaining why. The code freeze workflow can be overridden by code reviewers. See pinned issues for any active code freezes with guidance.
Note: The Flutter team is currently trialing the use of Gemini Code Assist for GitHub. Comments from the
gemini-code-assistbot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.