You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Make sure these boxes are checked before submitting your issue:
[x] Check that your version of Python is 3.4+
[x] Check that you are on the newest version of Pyrebase
[x] Check that Email/password provider is enabled in your Firebase dashboard under Auth -> Sign In Method.
At least on my current Firebase project, the JSON configuration got from the Firebase console has no "databaseURL" key.
At least on my current Firebase project, the JSON configuration got from the Firebase console has no "databaseURL" key.
In previous days, the databaseURL key came by default in the firebase configuration json. The library still follows that pattern, and it makes sense to so, because it'll enable usage of all sub-modules at once.
I maintain a version of pyrebase/pyrebase4 repo, and in the documentation for that project, I've mentioned about the key here.
Coming across the same issue I came across a SO post that the URL is no longer needed to authenticate. So I passed None for both databaseURL and storageBucket (since Im not using cloud storage and Im using firestore not the RTB). I could authenticate just fine.
Make sure these boxes are checked before submitting your issue:
[x] Check that your version of Python is 3.4+
[x] Check that you are on the newest version of Pyrebase
[x] Check that Email/password provider is enabled in your Firebase dashboard under Auth -> Sign In Method.
At least on my current Firebase project, the JSON configuration got from the Firebase console has no "databaseURL" key.
Instead, the keys are:
That means that the following line of
pyrebase.Firebase.__init__
throws an exception:Pyrebase4/pyrebase/pyrebase.py
Line 36 in 3e00233
The fix seems to be to replace that line with the following code
but I don't know if that has knock-on consequences elsewhere in the codebase.
The text was updated successfully, but these errors were encountered: