Closed tombouquet closed 1 year ago
@RustedBuckett Does this still happen if you remove next-firebase-auth
from the project entirely? I'd like to confirm it's not some other error with Firebase or Firebase UI.
After removing next-firebase-auth
the problem still occurred. I found that the problem had to do with returning custom claims on a sign in method that didn't support it. (https://firebase.google.com/docs/auth/extend-with-blocking-functions#supported_credentials)
Describe the bug When blocking functions are enabled, authentication fails. In my case I was returning 'sessionClaims' to the user (see https://firebase.google.com/docs/auth/extend-with-blocking-functions#modifying_a_user).
Blocking functions DO work however when using the Firebase emulators.
Versions
next-firebase-auth
version: 0.14.4 Firebase JS SDK: 8.9.1 Next.js: 12.2.3To Reproduce Steps to reproduce the behavior:
Note that I first discovered this on my own project which is on the latest versions of Firebase & the v1.0.0-canary.17 version of next-firebase-auth - however moved over to the example project to eliminate variables
Expected behavior The user should login with the proper returned user object. (basically it should work ah)
Debug and error logs