The State Changer participants focused on addressing Nathan's error message regarding Flutterflow maps. The meeting highlight was the challenge they faced to display Google Maps correctly using Flutterflow. Initially, Nathan suspected an error concerning font files and shared his experience of unsuccessful attempts to seek clarification from Google.
Key issues raised were the non-display of Google Maps correctly, potential issues with incorrect linking of Google Accounts within the console, problems arising when Flutterflow and Flutter versions come out of sync, and the evolution of progressively different versions of Flutter underneath Flutterflow. The team suggested running a "clean room" diagnostic by experimenting with the same problem on a separate project. If the issue persists across both, there's likely a larger problem with Google Maps on Flutterflow. Some other suggestions included placing it in a container or potentially addressing issues with customized fonts. Other alternatives to Google Maps mentioned include Mapbox and Radar. However, the overall consensus was that Google Maps remained the gold standard due to its cost-effectiveness, despite potential faults. The meeting ended with a transition to the next discussion led by Amir, while also planning to revert to any pending issues by Bailey.
(Source: Office Hours 2/27 )
