Firebase Auth - not working

[Jens_Limbach]

Dear AppGyver Team,

first: great job on your video how to connect Firebase: Google Firebase connector - Composer

The Todo data base example worked right away!

But the Authentication always tells me that my entered data is wrong. I really don’t know what I could have missed as the steps are very easy: enable auth in firebase for email/pw → create a user → enable auth in composer → test it…

If you have any idea what I missed I would be very thankful… I will try the next days to do it maybe all from scratch but as the ToDo list works very well I assume I have setup all correct…

Thanks
Jens

[Mari]

Hi Jens, glad to hear you liked the tutorial! Looks like there is in fact something wrong with the Firebase auth, I wasn’t able to get it working either. I’ll report the issue forward, thanks for reaching out!

[escapenewhaven]

Having the same issue. Glad I checked here after only an hour of trying to troubleshoot

Based on experimenting with my Firestore security rules, it seems that AppGyver is successfully communicating to Firebase Auth that I am authenticated (“request.auth != null” passes), but not communicating which username I’m authenticated under (any rules that match usernames fail with error 403).

[Mari]

@Jens_Limbach, did you also configure the Web app? I had forgot to fill in the web app name and API key, which resulted in the auth not working in the preview.

@escapenewhaven – what does your Firebase security rule look like?

[escapenewhaven]

@Mari I’m using the exact set of rules that they use in the second example here.

My setup is very simple: the user authenticates, then can access the document in the “users” collection that corresponds to their username. I am passing their username via variable into the document identifier and it seems to be resolving in the correct URL for the GET request. Unfortunately no matter what I try I keep getting a 403 permission error – unless I simplify the rules to allow all authenticated users to access everything (the commented-out lines in the rules screenshot), which works for testing most parts of the app but is not going to work in production.

I am building with 2.8.33.

[escapenewhaven]

When I run the same operation in the Rules Playground, it is successful.

[Mari]

Looks like uid in this case is a Firebase assigned id to the user (if you check on the Authentication tab, each user has an UID that is a string), but your custom collection “users” is using email as record identifier. So when you have a rule like

allow read, write: if request.auth != null && request.auth.uid == userId;

the request.auth.uid is a string, but it’s getting compared to an email.

Would it work if you try to update the rule to

allow read, write: if request.auth != null && request.auth.token.email == userId; ?

[escapenewhaven]

You are 100% right

[nkwazi_wez]

Hi, how did you connect the user UID or email to firestore?

[Jens_Limbach]

@Mari : Thank you so much! It immediatly worked after adding the web app details in the AppGyver configuration for firebase! Thank you so much for you super fast help!

[Jens_Limbach]

@Mari : It works now on the Web App. But the iOS Preview App crashes now the moment I open it. When I remove the Auth its working again… Any ideas?

[Mari]

Hi @Jens_Limbach , have you configured the iOS app?

[Jens_Limbach]

Dear @Mari , I am so sorry it was also here my mistake… I switched the app id and the client id… For sure it cannot work… Thanks for asking exactly the right questions! It is now all working fine!