You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the getAdminAuth() is always called regardless of the fact you may not have a service account.
If you move the const adminAuth = getAdminAuth(firebaseAdminApp) inside the if block if (auth.currentUser?.uid !== uid) the problem goes away, or maybe it should be here
to add a if block if (nuxt.options.ssr && hasServiceAccount)
Additional information
Our use case is that, we don't have a service account because we don't need to render anything on the server based on authentication state, we are only using authentication on client side in some <client-only /> components
The text was updated successfully, but these errors were encountered:
Reproduction
vuefire/packages/nuxt/src/runtime/auth/plugin-authenticate-user.server.ts
Line 20 in 687ce09
Steps to reproduce the bug
Make sure you don't have the
GOOGLE_APPLICATION_CREDENTIALS
setRun
npm run dev
or build for productionExpected behavior
You should be allowed to use auth module without a service account
Actual behavior
You get this error when using the auth module without a service account specified.
The default Firebase app does not exist. Make sure you call initializeApp() before using any of the Firebase services
I think the problem comes from here
vuefire/packages/nuxt/src/runtime/auth/plugin-authenticate-user.server.ts
Line 20 in 687ce09
the
getAdminAuth()
is always called regardless of the fact you may not have a service account.If you move the
const adminAuth = getAdminAuth(firebaseAdminApp)
inside the if blockif (auth.currentUser?.uid !== uid)
the problem goes away, or maybe it should be herevuefire/packages/nuxt/src/module.ts
Line 203 in 687ce09
to add a if block
if (nuxt.options.ssr && hasServiceAccount)
Additional information
Our use case is that, we don't have a service account because we don't need to render anything on the server based on authentication state, we are only using authentication on client side in some
<client-only />
componentsThe text was updated successfully, but these errors were encountered: