Connect FlutterFlow to Proxy Mail QA
FlutterFlow’s AI doesn’t connect its builder AI to other tools (it lets other AI tools work on your app instead), so there’s nothing to connect Proxy Mail QA to there. Test from your browser instead.
For the web version of your app: Proxy Mail QA for Chrome fills the sign-up form with a test address and shows the code or link when the email arrives. Open your app (not the editor) in its own tab, click the extension and turn it on for that address. Proxy Mail QA for Chrome has more.
For the app on a phone or simulator, the mobile guides and the Flutter helper make a test address in your test, wait for the email and give you the code or link to open in the app.
Set where links lead
- Firebase. Add your app’s web address under Authentication → Settings → Authorized domains in the Firebase console, or the links it sends are refused.
- Supabase. Set Site URL and add every address links may lead to, including your app’s deep link, under Authentication → URL Configuration.
Sender and custom email
Firebase and Supabase both send from their own address until you set yours. Supabase’s built-in sender only sends a few emails an hour, so a round of test sign-ups soon runs into it; add your own SMTP server under Authentication → Emails before testing much. Sign-in email limits covers each service.
Clear out test users
Every test sign-up leaves a user in your app. When you’re done, open Project settings → Test users to delete in Proxy Mail QA: it lists every test address the project used, live or gone, and the domains they end in, so you can find them all in your user list. Then delete them under Authentication → Users in Firebase or Supabase.