FlutterFlow / flutterflow-issues

A community issue tracker for FlutterFlow.
98 stars 17 forks source link

Able to save data in Firestore via debug, but Firestore rule state 'Write' - 'No One' #2827

Closed vengoran closed 1 week ago

vengoran commented 3 weeks ago

Has your issue been reported?

Current Behavior

Data is getting stored in Firestore database but the rules states 'Write' - 'No One' FlutterFlow to Firestore Issue.docx

Expected Behavior

Data should not be stored in Firestore as per the Flutterflow document

Steps to Reproduce

  1. Run the app in test mode
  2. Add a note and save the note

Reproducible from Blank

Bug Report Code (Required)

ITFfismB25NgoctH176JcsJvuCAvJmEcTIMziNZ+exUbfaL1BqQMfMjSYVhtUtOgaVNcC06jrD4Jwa3whYXuVvU5ExKdQa5SzpZybAzee2iWV4ysC7q8PmskL+lTIXHG08GFkBBCPuNYLEJh6173G9yXEzDDFOu/Zwh9f6PHaOI=

Context

Standard functionality not working as expected

Visual documentation

FlutterFlow to Firestore Issue.docx

Additional Info

No response

Environment

- FlutterFlow version: 4.1.45
- Platform: Flutterflow
- Browser name and version: Firefox
- Operating system and version affected: NA

General

Relative to the time the changes were made, data was lost within

When following my steps to reproduce, data loss happens

ignalauret commented 2 weeks ago

Hey @vengoran thanks for your report. First of all, I can see you are confusing the Write permission with the Create permission.
From the Docs:

I can see that in your project you have Create enabled for "Everyone", so it's correct that you are able to create documents from your app.
However, I also tried setting this Create to "No One" on a project I created to replicate your issue, and I was still able to create documents. This was because my project was new, so I had a "Test Rule" inside my Firestore rules that allowed every interaction with my DB until certain date next month.
So, please make sure to disable the Create flag instead of the Write flag, and also remove the "Test Rule" if you have it.
Hope I was helpful, I'm closing this issue because I don't see any bug here. If you still think there is a bug, please let me know.
Have a great day!

github-actions[bot] commented 1 week ago

This issue is stale because it has been open for 7 days with no activity. If there are no further updates, a team member will close the issue.