firebase_auth signInAnonymously() fails with PlatformException(channel-error) — Supabase Auth project, Push Notifications toggle OFF

Troubleshooting
Resolved

I'm implementing silent Firebase Anonymous Login alongside Supabase Auth, per FlutterFlow's own documented recommendation (Push Notifications docs: "consider implementing Anonymous Firebase Login" for users who need FCM tokens registered even while logged out of Supabase).

Setup:

- Authentication Type: Supabase (Push Notifications toggle is OFF, since it's incompatible with Supabase Auth)

- Custom Pub Dependencies: firebase_auth 5.3.3, firebase_core 3.6.0, firebase_messaging 15.2.7, mobile_scanner 5.2.3

I added a Custom Action that calls Firebase.initializeApp() (if not already initialized) then FirebaseAuth.instance.signInAnonymously(). On a real Android device, fresh release-signed APK install, this fails every time with:

PlatformException(channel-error, Unable to establish connection on channel., null, null)

Anonymous sign-in is enabled in Firebase Console (Authentication > Sign-in method). SHA-1 fingerprint is registered and matches my upload keystore. No new Firebase user ever appears in the console after this runs.

My question: is there a known-good version pairing for firebase_auth + firebase_core that works with FlutterFlow's current build pipeline for this pattern, or a required build/cache step I'm missing?

What have you tried so far?

- Confirmed Anonymous provider is Enabled in Firebase Console

- Confirmed SHA-1 fingerprint is registered correctly in Firebase Console and matches my keystore

- Added firebase_auth and firebase_core as explicit Custom Pub Dependencies with pinned versions (5.3.3 and 3.6.0)

- Did a full fresh APK rebuild (not just recompile) after adding/pinning these

- Confirmed the error is specific to this new code — no other part of the app is affected

- Added temporary debug logging that writes the exact error string to my own database, confirming this exact PlatformException every time

Did you check FlutterFlow's Documentation for this topic?
Yes
2
3 replies