python-firebase | Python interface to the Firebase 's REST API | REST library

Your code uses get, which gets the data and immediately continues

To listen for data, follow the documentation on streaming updates. From there:

You forgot to add the gunicorn library to your requirements.txt. Without gunicorn, the web app cannot start as it is the HTTP server. To fix this, just add gunicorn==20.0.4 to your requirements.txt and it should work.

The problem is that you are using sequential numeric keys for the records in node 'PatientMaster' and the record contents are very similar. Firebase RTDB interprets (sometimes) that structure as a list array rather than a map array. The reason being that when you post a list array to FB RTDB it stores it as a map (json) with keys 0-n and the list items as the values. When you read the db and it sees this structure it thinks it is a stored list array and returns that instead of a map (json). See this post: https://firebase.googleblog.com/2014/04/best-practices-arrays-in-firebase.html?m=1

You need to make your keys more complex, or test / expect the data returned from this node to be a list array.

The python-firebase project was last released on March 21, 2014 by a third-party developer and doesn't support Python 3.7. Specifically it uses the new reserved keywords async/await.

You probably want to use the google-cloud-firestore client library instead, which is maintained and supported by Google.

I think you need python_jwt instead of jwt. You can do:

pip install python_jwt

When you you the Firebase Admin SDK on any platform, there is no sense of current logged in user. The Admin SDK gives you privileged access to Firebase and Cloud products using a service account for authentication and authorization. It doesn't use a Firebase Authentication account.

Only the mobile and web clients have a sense of currently logged in user, because they require the user to authenticate in order to gain acccess.

In order to use the Admin SDK with a project, you must have access to the service account credentials for that project. And with those credentials, you have full and unlimited access to the project. You should only distribute the service account credentials to users who should have such access, typically the collaborators on the project.

For application level administrators that are not collaborators on the project, I typically recommend setting up an administrative dashboard with a server-side and a client-side component.

The server-side component runs in a trusted environment, which for me often is Cloud Functions, but can also be a server you control, or even your development machine. This is where you use the Admin SDK to perform application administration actions, which you then expose in an authenticated end-point that client-side applications can call.

The client-side component is what the application administrator uses. For me this is often a very simple web page, but it can also be any other technology you prefer, as long as it can call the end points you exposed on the server.

The key here is that the server validates that the user that calls it is authorized to do so, before executing administrative actions on their behalf. With this approach, you don't have to give the service account credentials to a non-collaborator, and can revoke the administrator's credentials if needed.

In pycharm, open 'Terminal'. In it run command

I reached out to the creator of the package, and he notified me that they'll look into the issue.

In the meantime, I used requests to access Firebase. I created a tutorial for the the community. Here is the link to the GitHub page: https://github.com/Petar-Luketina/Firebase-Sample . If the code is unclear, there's a link to my YouTube tutorial in the README.md.