The State Changer meeting focused on the setup and troubleshooting of Flutter, specifically its integration with FlutterFlow. The discussion revolved around Flutter SDK versioning, installation issues, and setting up the PATH for multiple versions of Flutter. One issue raised was that the stable Flutter version was not working properly with FlutterFlow.
Key Points: 1. The participants discussed whether they individually installed Flutter or if Android Studio facilitated the process. 2. Issues were raised about identifying the right SDK version for FlutterFlow, with participants agreeing to share any available documentation. 3. A participant asked about handling multiple SDKs and if there's a process to reset or clean them; the recommended solution was to organise the PATH effectively, prioritising the required Flutter version. 4. Another participant raised a problem with the Flutter Flow stable version not working with the current stable from Flutter, highlighting the need to keep track of versions and updates. They discussed obtaining specific versions and how to add them to the PATH. 5. There was a general consensus about using Flutter 3.7 but acknowledged that could change depending on FlutterFlow updates. No mentions were made of the keywords "Xano", "WeWeb", "Zapier", "Make", "Integromat", "Outseta", "Retool", "Bubble", "Adalo", "AppGyver", "AppSheet", "Comnoco", "Fastgen", "Firebase", "Google", "OAuth", "Stripe", "Twilio", "Airtable", "DraftBit", "Javascript", "Typescript", "React", "Vue.js", "JSX", "HTML", "CSS", "lambda", "serverless", "State Change", "ScriptTag", "OpenAI", or "AI21".
(Source: Office Hours Extra - Flutterflow Export 6/5 )
