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
[google_maps_flutter] Add support for heatmap layer #33586
Heatmap support is implemented for both Android & iOS in PR flutter-team-archive/plugins#2454 but I am having trouble getting the podspec file to build because Google-Maps-iOS-Utils is a static framework dependency.
The build_all_plugins_ipa task gives the following error:
[!] The 'Pods-Runner' target has transitive dependencies that include statically linked binaries
Does anyone know how to include the Google-Maps-iOS-Utils dependency without breaking the build?
After looking into the google-maps-utils repo, I want to experiment to have a separate flutter plugin to handle all the features in the google-maps-utils. I will set up the new plugin and add some minimum code. After that, we can work together to add these new features. Including heat-map mentioned in this issue.
This issue is marked P1 but has had no recent status updates.
The P1 label indicates high-priority issues that are at the top of the work list. This is the highest priority level a bug can have if it isn't affecting a top-tier customer or breaking the build. Bugs marked P1 are generally actively being worked on unless the assignee is dealing with a P0 bug (or another P1 bug). Issues at this level should be resolved in a matter of months and should have monthly updates on GitHub.
Please consider where this bug really falls in our current priorities, and label it or assign it accordingly. This allows people to have a clearer picture of what work is actually planned. Thanks!
This issue is marked P1 but has had no recent status updates.
The P1 label indicates high-priority issues that are at the top of the work list. This is the highest priority level a bug can have if it isn't affecting a top-tier customer or breaking the build. Bugs marked P1 are generally actively being worked on unless the assignee is dealing with a P0 bug (or another P1 bug). Issues at this level should be resolved in a matter of months and should have monthly updates on GitHub.
Please consider where this bug really falls in our current priorities, and label it or assign it accordingly. This allows people to have a clearer picture of what work is actually planned. Thanks!
Anyone is welcome to add comments to flutter/packages#3257 if they have feedback that they would help advance the PR.
(Since this issue has attracted a lot of "me too"-type comments, I want to clarify that comments on the PR need to focused on constructive feedback; "+1" or "me too" will only slow progress by wasting the time of the people working on the PR.)
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
XinyueZ commentedon Jun 13, 2019
Rob-Biemans commentedon Jun 16, 2019
urmilshroff commentedon Aug 16, 2019
jerfeson commentedon Aug 29, 2019
DCubix commentedon Oct 14, 2019
clemclx commentedon Oct 24, 2019
fvisticot commentedon Nov 13, 2019
MpEliaz commentedon Dec 27, 2019
SvenSlijkoord commentedon Jan 11, 2020
Heatmap support is implemented for both Android & iOS in PR flutter-team-archive/plugins#2454 but I am having trouble getting the podspec file to build because
Google-Maps-iOS-Utilsis a static framework dependency.The
build_all_plugins_ipatask gives the following error:Does anyone know how to include the
Google-Maps-iOS-Utilsdependency without breaking the build?arok commentedon Jan 22, 2020
@SvenSlijkoord googlemaps/google-maps-ios-utils#23
cyanglaz commentedon Jan 27, 2020
After looking into the
google-maps-utilsrepo, I want to experiment to have a separate flutter plugin to handle all the features in thegoogle-maps-utils. I will set up the new plugin and add some minimum code. After that, we can work together to add these new features. Including heat-map mentioned in this issue.lbk9 commentedon Jan 30, 2020
46 remaining items
flutter-triage-bot commentedon Nov 29, 2023
This issue is marked P1 but has had no recent status updates.
The P1 label indicates high-priority issues that are at the top of the work list. This is the highest priority level a bug can have if it isn't affecting a top-tier customer or breaking the build. Bugs marked P1 are generally actively being worked on unless the assignee is dealing with a P0 bug (or another P1 bug). Issues at this level should be resolved in a matter of months and should have monthly updates on GitHub.
Please consider where this bug really falls in our current priorities, and label it or assign it accordingly. This allows people to have a clearer picture of what work is actually planned. Thanks!
stuartmorgan-g commentedon Dec 5, 2023
This is in progress; keeping P1.
flutter-triage-bot commentedon Apr 9, 2024
This issue is marked P1 but has had no recent status updates.
The P1 label indicates high-priority issues that are at the top of the work list. This is the highest priority level a bug can have if it isn't affecting a top-tier customer or breaking the build. Bugs marked P1 are generally actively being worked on unless the assignee is dealing with a P0 bug (or another P1 bug). Issues at this level should be resolved in a matter of months and should have monthly updates on GitHub.
Please consider where this bug really falls in our current priorities, and label it or assign it accordingly. This allows people to have a clearer picture of what work is actually planned. Thanks!
ZhuBoao commentedon Apr 11, 2024
stuartmorgan-g commentedon Apr 23, 2024
The PR had been blocked on a significant API wrapping issue, but that has been resolved an the PR is once again making good progress.
trevor-nomadik commentedon May 8, 2024
Anyway I can help? Would definitely solve one of my current problems.
stuartmorgan-g commentedon May 8, 2024
Anyone is welcome to add comments to flutter/packages#3257 if they have feedback that they would help advance the PR.
(Since this issue has attracted a lot of "me too"-type comments, I want to clarify that comments on the PR need to focused on constructive feedback; "+1" or "me too" will only slow progress by wasting the time of the people working on the PR.)
[google_maps_flutter] Add heatmap support (#3257)
wangela commentedon Aug 13, 2024
Heatmap layer support has been released for apps targeting Android, iOS, and web in google_maps_flutter v2.8.0 🚀
github-actions commentedon Aug 27, 2024
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.