Regression: Authenticated User → User Reference missing, existing Firestore bindings changed to "Unknown"

[raviiipatil-ai]

Can we access your project?

• I give permission for members of the FlutterFlow team to access and test my project for the sole purpose of investigating this issue.

Current Behavior

Subject: Critical FlutterFlow Regression – Authenticated User "User Reference" Missing, Breaking Existing Firestore Bindings

Hello FlutterFlow Support Team,

I believe I've encountered a platform regression after opening my project following approximately 15 days of inactivity.

Project Details

Project: indus-385ml2
Firebase project: indus-d52b4
Last known error-free state: ~15 days ago (untouched since)
Current state: 8 errors, Run Mode blocked with "Fix errors in the project before running..."
Last production deploy (unaffected, currently live): June 15, 2026 — indus-385ml2.flutterflow.app FamRely
Authentication: Firebase Authentication (Phone OTP)
Database: Firestore
Plan: Paid FlutterFlow

What happened

About 15 days ago:

• The project compiled successfully.
• There were 0 editor errors.
• The application was running correctly.

After opening the same project today (without making any changes), FlutterFlow now reports multiple errors.

Errors shown

Field "customerRef" is not properly set in Database action
Field "userRef" is not properly set in Database action
Multiple Firestore Query errors:

One or more filters are invalid

(One Navigation error was caused by me deleting an old page and has already been fixed.)

Investigation performed

I verified the following:

✅ users collection still exists.

✅ Firestore schema is intact.

Examples:

bookings.customerRef → Document Reference (users) user_addresses.userRef → Document Reference (users)
packageRef, categoryRef, providerRef are all correctly defined.

The Firestore schema has not changed.

Root issue

Previously, these bindings were using:
Authenticated User
→ User Reference

However, now every existing binding has become:
Unknown

When I try to reconnect it, FlutterFlow opens the variable picker for:
Type:
Document Reference (users)

but under Authenticated User, I only see:

• Email
• User ID
• Display Name
• Photo URL
• Phone Number
• Email Verified
• ID Token (JWT Token)

There is no "User Reference" option anymore.

Because of this, I cannot reconnect any Firestore fields or query filters that require a Document Reference (users).

Result

Existing actions such as:

• Create Booking (customerRef)
• Save Address (userRef)
• Firestore Queries (userRef == authenticated user)

can no longer be configured because the required authenticated document reference is missing.

Why I believe this is a FlutterFlow regression

• The project previously worked correctly.
• No Firestore schema changes were made.
• Authentication configuration is unchanged.
• Existing bindings have automatically become Unknown.
• The required **Authenticated User → User Reference option is no longer available in the variable picker.

Additional impact: Run Mode is now fully blocked with "Fix errors in the project before running..." — I cannot test or validate any further work until this is resolved. My last production deployment (June 15, 2026, live at indus-385ml2.flutterflow.app) is unaffected and still running correctly for end users, but I'm unable to build, test, or ship anything further in the meantime.

Could you please confirm whether this is a known issue or regression and advise on the recommended fix?

Thank you for your assistance.

Kind regards,
Ravi

Expected Behavior

Existing Firestore bindings that use "Authenticated User → User Reference" should continue to work after reopening the project.

The variable picker should provide "Authenticated User → User Reference" whenever a Document Reference (users) is required.

Existing bindings should not automatically become "Unknown", and Firestore Query/Update actions should not become invalid without any schema changes.

Steps to Reproduce

1. Open an existing FlutterFlow project that previously used "Authenticated User → User Reference" in Firestore Query and Firestore Update actions.

2. Reopen the project after updating FlutterFlow.

3. Open any Firestore Query or Firestore Update action that filters or writes a Document Reference (users).

4. Observe that the previous binding has changed to "Unknown".

5. Click the variable picker.

6. Under "Authenticated User", only Email, User ID, Display Name, Phone Number, etc. are available. "User Reference" is missing.

7. Because the Document Reference cannot be selected, the query/action becomes invalid.

Reproducible from Blank

• The steps to reproduce above start from a blank project.

Bug Report Code (Required)

Unable to generate Bug Report Code because the issue affects multiple pages and existing Firestore bindings.

Visual documentation

Attached screenshots show the regression. Existing Firestore bindings changed to "Unknown" because "Authenticated User → User Reference" is no longer available in the variable picker.

Environment

- FlutterFlow version: v7.0.33 (Released July 18, 2026)
- Platform: Web
- Browser name and version: Google Chrome Version 150.0.7871.125 (Official Build) (64-bit)
- Operating system and version affected: Windows 10 Home Single Language 22H2 (64-bit)
Additional project information:
- Flutter SDK: 3.38.6
- Firebase Authentication: Phone Authentication
- Firestore Database

Additional Information

This issue affects multiple pages throughout the project.

Previously working Firestore bindings have automatically become "Unknown", making existing Firestore Query and Firestore Update actions invalid.

The Firestore schema has not changed. The only missing item is "Authenticated User → User Reference" in the variable picker.

I have attached screenshots showing:

• Existing bindings changed to "Unknown"
• Missing "User Reference" under Authenticated User
• Firestore errors generated by this regression

This appears to be a regression rather than a project configuration issue.

[Alezanello]

Hello! 👋

To resolve this issue, go to your Firebase collection settings and enable the Users collection. Once it's enabled, the issue should be resolved.

[raviiipatil-ai]

Thanks for the quick response.

That was exactly the issue.
The selected collection had become Unset. After selecting users in FlutterFlow → Firebase → Settings and running Validate, the project immediately recovered:

Authenticated User → User Reference became available again.
Firestore queries no longer showed Unknown.
All analyzer errors disappeared.

This may help other developers who encounter the same symptoms after opening an existing project.

Thanks for the quick assistance!

[raviiipatil-ai]

Thanks for the quick response. That was exactly the issue. The selected collection had become Unset. After selecting users in FlutterFlow → Firebase → Settings and running Validate, the project immediately recovered: Authenticated User → User Reference became available again. Firestore queries no longer showed Unknown. All analyzer errors disappeared. This may help other developers who encounter the same symptoms after opening an existing project. Thanks for the quick assistance!

…

On Mon, Jul 20, 2026 at 10:45 PM Ale Zanello ***@***.***> wrote: *Alezanello* left a comment (FlutterFlow/flutterflow-issues#7306) <#7306 (comment)> Hello! 👋 To resolve this issue, go to your Firebase collection settings and enable the *Users* collection. Once it's enabled, the issue should be resolved. [image: image.png] <https://camo.githubusercontent.com/efa4167ab5e6c77eb4162db3b56469cbe015e06bca25c606cdef3d82f3b928dd/68747470733a2f2f75706c6f6164732e6c696e6561722e6170702f33323431303839642d373336612d343432322d393030622d3035316537326163636462652f30316638383635612d613139342d343263662d393663342d3232626239326565613235642f33643931626331642d613735322d346335332d613233652d6464326162353662376338333f7369676e61747572653d65794a68624763694f694a49557a49314e694973496e523563434936496b705856434a392e65794a775958526f496a6f694c7a4d794e4445774f446c6b4c54637a4e6d45744e4451794d6930354d4442694c5441314d5755334d6d466a593252695a5338774d5759344f445931595331684d546b304c545179593259744f545a6a4e4330794d6d4a694f544a6c5a5745794e5751764d3251354d574a6a4d575174595463314d693030597a557a4c5745794d3255745a475179595749314e6d4933597a677a4969776961574630496a6f784e7a67304e5459334e7a45774c434a6c654841694f6a45344d5459784d7a67794e7a42392e672d47523975764d665855665a73744e323133616b646f7071395a564e3771746f39466e546c594771356720> — Reply to this email directly, view it on GitHub <#7306?email_source=notifications&email_token=CJGPNYP2VYMJORDYOU2GVLL5FZHTJA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBSGUYDEOJYGMZ2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-5025029833>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/CJGPNYLWPOWY4MJIGGREPMT5FZHTJAVCNFSNUABFKJSXA33TNF2G64TZHM2TENZQG4ZTQNJWHNEXG43VMU5TIOJSG42TGNJYGA4KC5QC> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/CJGPNYKMS3YGXR57EPOT2PD5FZHTJA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBSGUYDEOJYGMZ2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG> and Android <https://github.com/notifications/mobile/android/CJGPNYIAIHEP2Y32XVJQ3C35FZHTJA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBSGUYDEOJYGMZ2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***>