In this meeting, the State Changers were troubleshooting an issue with the automation process in Flutterflow. Specifically, when a particular button was pressed, it appeared that the automation was not functioning correctly. Although static content was being shown, the dynamic elements were not.
This led to a deep dive into several components of the workflow, including the point redemption document, the API request, the value being pulled from the widget state slider, and the document creation process. Using tools like Pipedream, Firebase, and several API calls and webhook integrations, the team worked together to identify possible issues and create potential fixes.
One significant issue revealed was that although data was correctly recorded in one instance, the ID was not changing in subsequent instances, indicating a problem with the data entry and retrieval process. Furthermore, input privacy was discussed, and the team explored potential issues related to maintaining privacy while also ensuring the correct function of the automation.
In the end, a potential solution was found to the problem in unmarking a specific API call as private. This action was hypothesized to have solved the problem by removing Flutterflow's additional proxy step in relaying information, causing the issue. Reinforcing the success of the automated process while ensuring data privacy was maintained was deemed crucial in ultimately resolving the problematic aspects of this function.
Keywords mentioned: "Flutterflow", "Firebase", "Pipedream".
(Source: Office Hours 5/22 )