You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Revive the "set marker icon" sample for Google Maps #33438
Following a breaking change to the ImageStream API in the framework(#32936) the Google Maps plugin sample app needs to be updated to the new API.
As we make sure to keep plugins working agains stable we cannot apply the update before the framework change makes it to stable. But if we do not apply the change, the plugins' CI is red as it's running with master.
For now, I'm updating the sample app to the new framework API, but commenting out the "set marker icon" sample until the framework change makes it to master.
Once the framework change makes it to stable we should uncomment that code.
I don't understand the question. Nobody has verified that the sample code is no longer commented out—they can't possibly have, because it isn't—which is what this bug is tracking.
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
amirh commentedon May 28, 2019
@iskakaushik
amreniouinnovent commentedon Aug 30, 2019
@amirh I think #32936 is merged to master
I tested the uncommented code and it is working for me
kleeb commentedon Nov 28, 2019
for me as well
9 remaining items
stuartmorgan-g commentedon Jun 16, 2021
I don't understand the question. Nobody has verified that the sample code is no longer commented out—they can't possibly have, because it isn't—which is what this bug is tracking.
stuartmorgan-g commentedon Jul 4, 2025
This was fixed in flutter-team-archive/plugins#2443
github-actions commentedon Jul 21, 2025
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.