Firebase Realtime Database Automatically Changing the Rules

[Akshun_Tapuriah]

Hi.

I have made an app that uses the FirebaseDB component to enable a user to Register and Login. I am using a custom Firebase Project, not the Default one.
Till a few days back, everything was working well with the app. (In both - The downloaded .apk and in the Companion.)

But today, when I opened the app (.apk) , an error popped up on the Login Screen - It showed "Firebase Error". I checked the Database in the Firebase Console, and the rules had automatically changed from ".read": true, ".write": true to ".read": false, ".write": false ..

Please help me solve this issue. I have changed the rules back now, but I am submitting this app for a competition, and I don't want this error to come when the judges check it.

Thanks in Advance

[TIMAI2]

This sounds like a Firebase problem. Your open settings may have been on a timer in Firebase, they write a rule that gives 30 days of open rules, then change the rules to secure rules.

[Akshun_Tapuriah]

Hi @TIMAI2

Thanks.

@TIMAI2

Your open settings may have been on a timer in Firebase, they write a rule that gives 30 days of open rules, then change the rules to secure rules.

So how should I disable this feature?

Please let me know.

[TIMAI2]

If you have changed your rules to read:true; write:true again, and you get no notices or warnings from Firebase, then you should be OK to carry on with open rules.

Firebase Security Awareness!

If like many developers, you use firebase for an online database, or for storage, and you are running your own instance of firebase, not the MIT provided instance, then you should be aware of the need to secure your data when in production. If you are working with other peoples personal data, you have a duty to protect it. For development you can set read and write as true which makes life a little easier, but when you come to production you MUST tighten up your rules, and have some form of se…

If you are still unsure, show your current rules (everything in rules) here...

[Akshun_Tapuriah]

Hi Tim,

I changed the rules back to
{
"rules": {
".read": true,
".write": true
}
}
(That's all that is there in the rules)

It did not send me a warning this time, So I'm assuming all is fine.
If I face the same problem again, I'll ask you.

Thanks a lot @TIMAI2