Hey Community. I have found this bug/issue in flutterflow that i have discussed with their support and they have agreed that this is an issue. I'm bringing it up to the community since i think this is an issue that is affecting many users with or without their knowledge. This issue affects API call users who are trying to use googlemaps. Basically if a user clicks a map marker there is no way to retrieve the latlng from that map marker. Flutterflow offers a two features "center on marker tap" and widget parameter "current map center" for passing into a receiving widget/app state variable/page parameter. However, these features only work with firebase.
Flutterflow googlemaps widget provides the "center map on marker tap" option to allow users to retrieve the center of the map latlng after a center on map tap has occurred. So the expected sequence is: clicked on marker, map centers on marker, then center of map/marker value is passed into whatever action/widget/parameter is expecting it.
However, what is actually happening is this: clicked on marker, current center of map is passed into whatever action/widget/parameter is expecting it, then map centers on map marker.
This bug has been reported but i want the community to be aware and collect some feedback so flutterflow can see how much this is actually impacting everyone. Based on my experience i suspect its alot. Here is the link to the bug on github:
with API Call Clicked Marker Event Listener · Issue #1762 · FlutterFlow/flutterflow-issues (github.com)
and if you are too lazy to click it then here are teh details below of what is happening:
Current Behavior
There is an issue when using googlemaps widget with API calls. the issue is related to the "center map on clicked marker" and "current map center" features are not passing the correct latlng map center upon execution when using API calls. Here is a more detailed explaination of what is happening.
Expected Behavior
Flutterflow googlemaps widget provides the "center map on marker tap" option to allow users to retrieve the center of the map latlng after a center on map tap has occurred. So the expected sequence is: clicked on marker, map centers on marker, then center of map/marker value is passed into whatever action/widget/parameter is expecting it.
However, what is actually happening is this: clicked on marker, current center of map is passed into whatever action/widget/parameter is expecting it, then map centers on map marker.
Steps to Reproduce
The issue can be reproduced by using an api all with googlemaps with this configuration:
creating a map widget and setting the current location and single marker location to the global to the users current location
creating an app statement variable called "onclickedlocation"
on the map widget enable "center on map marker click"
then create an "on clicked marker" action.
this action then can update the "onclickedlocation" using the current map googlemaps center
Execution steps to reproduce:
put app in runtime
move map marker so it is anywhere but center of map
click map marker
the onclicked location app state variable will be set with teh current map center
then the map will center on the clicked marker.
onclickedlocation variable will now be set to the old center of map prior to the marker being moved to center of map
Reproducible from Blank
The steps to reproduce above start from a blank project.
Bug Report Code (Required)
ITESjM/lw49gocgE+anyb8dAhQMnQzM5U+cFjtt+Zw8hfbbvE6QDdeP4dlBLYterenNiBFCKrH0z+NGKiISWFfoFAyysfY9xzJRXQQKWZH2RWralDaqKY0RBN8JRGlyk3MCJvxBDANpuLX9l7EOTffCdG3qCf9qOYwx5e6fDbOY=
Context
my app design requires plotting of many latlng's from devices AWS IOT devices on google maps for our customers. We utilize AWS for all our serverless infrastructure and flutter was chosen to integrate with it. However, this issue is a 100% major issue. Not just because it affects us but because it go against the philosphy that was appealing to use with flutterflow. Flutterflow uses API calls but its internal features do not support those API calls. This is catastrophic result. We are in a extremely bad situation because of this issue as we need the marker click event to work with our API's so customers can utilize our data. i don't want it to be dramatic but this is 9/10 severity and priority level bug that needs to be addressehttps://files-us-east-1.t-cdn.net/files/hPx8sCu1tU0CVoVXk2O1u
