Niotron is so indifferent!

Discuss
1

Niotron is so indifferent! Two more updates came after he said the following. There is no similarity between his words and deeds. The bug has not been fixed yet. Gave some unnecessary updates. But it was most necessary.
adsdsafde

2

You can use Firebase auth API to solve this issue.

3

Shouldn’t Nitron solve it? 3 more updates came after I informed them of the problem. But it was not resolved.

4

I have one question, what’s your exact issue, firebase auth or Realtime database

5

The main problem is in the following two blocks. :point_down:

component_method

component_event
component_event1460×170 20.1 KB

The token does not come even after successful login. Can’t use real-time database for get tokens. Because without token the following rules will not work :point_down:.

{
    "rules" : {
        "users" : {
              "$user_id" : {
                  ".read" : "auth.uid == $user_id",
                  ".write" : "auth.uid == $user_id"
              }
          },
        "Notic" : {
            ".read" : "auth.uid != null",
            ".write" : "auth.uid != false",
          },
          "Pending Payment" : {
            ".read" : "auth.uid != null",
            ".write" : "auth.uid != null",
          },
          "Page" : {
            ".read" : "auth.uid != null",
            ".write" : "auth.uid != false",
          },
          "extra" : {
            ".read" : "auth.uid != null",
            ".write" : "auth.uid != null",
          }
    }
  }

:point_down: :point_down:

I also think there are problems with the rest of the firebase authentication blocks. All need to be checked.

1 Like