Repository navigation
[google_maps_flutter] Document tile cache flicker - #12315
Merged
auto-submit[bot] merged 2 commits intoSep 16, 2026
Merged
auto-submit[bot] merged 2 commits into
auto-submit[bot] merged 2 commits into
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Code Review
This pull request updates the google_maps_flutter package to version 2.18.1. The changes update the documentation for the clearTileCache method in GoogleMapController to clarify that clearing the tile cache may cause the tile overlay to flicker on some platforms. The CHANGELOG.md and pubspec.yaml files have been updated accordingly. There are no review comments to address.
stuartmorgan-g
self-requested a review
August 11, 2026 18:56
Contributor
|
Friendly ping for @stuartmorgan-g 🙂 |
stuartmorgan-g
approved these changes
Sep 9, 2026
stuartmorgan-g
left a comment
stuartmorgan-g
left a comment
Collaborator
There was a problem hiding this comment.
LGTM. Sorry for the delay, this fell through the cracks in my review tracking.
@tarrinneal or @bparrishMines for secondary review.
bparrishMines
added
the
autosubmit
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
4 participants
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.
Updates
GoogleMapController.clearTileCachedocumentation to explain that some platform implementations may remove current tiles before replacements are available, which can cause the tile overlay to flicker. The wording remains implementation-neutral so it also applies to third-party platform implementations.Fixes flutter/flutter#189678.
Pre-Review Checklist
[shared_preferences]///).Test exemption: This PR changes only API documentation and the required release metadata; it does not change runtime behavior.
Validation:
dart format --output=none --set-exit-if-changed packages/google_maps_flutter/google_maps_flutter/lib/src/controller.dartdart run script/tool/bin/flutter_plugin_tools.dart analyze --packages=google_maps_flutter/google_maps_flutter --exact-match-onlydart run script/tool/bin/flutter_plugin_tools.dart dart-test --packages=google_maps_flutter/google_maps_flutter --exact-match-onlydart run script/tool/bin/flutter_plugin_tools.dart validate --packages=google_maps_flutter/google_maps_flutter --exact-match-only --base-branch=upstream/maindart run script/tool/bin/flutter_plugin_tools.dart publish-check --packages=google_maps_flutter/google_maps_flutter --exact-match-onlyIf you need help, consider asking for advice on the #hackers-new channel on Discord.
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.Footnotes
Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling. ↩ ↩2