The State Changers meeting involved discussions mostly centered around integrations with Firebase App Check and deployment issues related to Google Play. The specific problem discussed had to do with the integration of Firebase App Check within a mobile application built through FlutterFlow. The participant had successfully set up Firebase and had followed FlutterFlow's instructions to integrate Firebase with AppCheck, with the integration working for the Web version of the application.
Issue arose when trying to verify requests coming from the Android version of the app. The participant was trying to use the Google Play Integrity API to verify the requests but was unable to see the 'Play Integrity' checks when testing via the Android emulator on his local machine. It was determined that despite successfully setting up Firebase and the client-side, the app had not been fully routed through Google Play to execute the integrity checks. The proposed solution was to deploy the version of the application with AppCheck enabled onto Google Play, not replacing the current version on the production channel, but onto a beta channel. Once live, the participant would revisit Firebase and check if Play Integrity is showing because it detected the signal. The main objective was to test regularly through Google Play to increase reliability for final customers. There was mention of other tools during the meeting like XML, SHA, and Debug Tokens, but the discussion was largely dominated by Firebase, Google Play, and FlutterFlow. The specifics of Airtable, Make, Zapier, Integromat, Retool, Bubble, Adalo, Outseta, AppGyver, AppSheet, Comnoco, Fastgen, OAuth, Stripe, Twilio, DraftBit, Javascript, Typescript, React, Vue.js, JSX, HTML, CSS, lambda, serverless, ScriptTag, OpenAI, or AI21 were not discussed in this meeting.
(Source: Office Hours 8/25/2023 )
