The State Changers conducted a meeting to discuss technical issues regarding their application. The primary issue was that the profile embed in their application, which was correlated with Outseta, was no longer functional. Additionally, the login embed also occasionally failed.
The meeting focused on resolving these issues. They used web development tools to assess the functionality and pinpoint any errors. The Outseta code was investigated, checking when and under what circumstances it was fired off. The team made sure to consider potential factors like internet speed and system differences causing discrepancies in issue occurrence. Their troubleshooting strategy included refreshing the page, clearing the cache, and performing a hard reset. They also tried to replicate the error on the login page with their cofounder to gather more information. Furthermore, they executed changes in their codebase, particularly around the initialization of profile data, and logged changes to the console for tracking. Lastly, they tested these changes and interpreted the results for further adjustments. This process involved tools like WeWeb and languages such as Javascript. The script did not mention the specific use of "Xano", "FlutterFlow", "Zapier", "Make", "Integromat, "Retool", "Bubble", "Adalo", "AppGyver", "AppSheet", "Comnoco", "Fastgen", "Firebase", "Google", "OAuth", "Stripe", "Twilio", "Airtable", "DraftBit", "Typescript", "React", "Vue.js", "JSX", "HTML", "CSS", "lambda", "serverless", "State Change", "ScriptTag", "OpenAI", or "AI21".
(Source: Office Hours 7/17/2023 )
