Place the right Security Rules back!
akauppi opened this issue · comments
Once firebase/firebase-js-sdk#4795 is resolved, change this back:
allow read: if true // HACK! CHANGE! so that development can continue! AK 15-Apr-21
//allow read: if isMember() && (!isRemoved() || isAuthor())
//&& validProject2() // optional: enable if you want to guard against bad data instead of letting client cope with it
Sam Stern mentioned at firebase/firebase-tools#3258
Right now neither fix has been released but when the next JS SDK and Emulator release go out either fix should be sufficient to stop this issue from happening.
i.e. Firestore Emulator 1.11.15 should suffice
done