Kevin Jennison

I verified this behavior. An authorizer with multiple identity sources requires all of them to be set, and if any are missing, it returns 401. This is consistent with [AWS...

Depending on your situation: another approach would be to include all relevant auth info to a single header, if your client is able to do so. Then, your authorizer could...

Did this work on 0.x and broke in canary, or does it also not work in 0.x? If possible, could you provide a reproduction (as simple as possible) in a...

Got it—thanks for the demo and explanation!

Thanks for the issue. This library just passes the `firebaseClientInitConfig` to `firebase.initializeApp` (see [here](https://github.com/gladly-team/next-firebase-auth/blob/main/src/initFirebaseClientSDK.js#L13)), so the config structure should be the same. Are you spelling `measurementId` correctly? Your issue description...

We could initialize analytics automatically if `measurementId` is set in `firebaseClientInitConfig`. This would be a small change to in [initFirebaseClientSDK.js](https://github.com/gladly-team/next-firebase-auth/blob/main/src/initFirebaseClientSDK.js). My only concern if is it would increase bundle size...

It's possible. As I mention above, we would just need to ensure that doesn't increase the bundle size for people who don't use the analytics functionality.

@davut You can initialize Firebase yourself. Here is some example code: https://github.com/gladly-team/next-firebase-auth/discussions/61#discussioncomment-323977 That isn't a "hack". This library initializes Firebase as a convenience, but it's totally fine to do it...

@davut If using Firebase v9, you'll want to use it _not_ in compat mode and alongside the [canary version](https://github.com/gladly-team/next-firebase-auth/tree/v1.x#readme) of `next-firebase-auth`.

Thanks for the issue. Agreed, this could be a nice optimization. What Firebase JS SDK API would work for this? If we implement this, we'd want logic to ensure a...