Firebase RTDB PERMISSION_DENIED when using compat in a worker

[jdcoldsmith]

Operating System

Windows 11

Browser Version

Chrome (latest version)

Firebase SDK Version

10.6.0 (compat)

Firebase SDK Product:

Auth, Database

Describe your project's tooling

Polymer, Lit, Rollup, Vitest

Describe the problem

Since transitioning from v8 to the new modular versions (v9 and v10), I have noticed a strange bug when trying to use firebase/compat/app in a worker. When using the compat 10.6.0 version in a web worker I will call firebase.initializeApp with the correct credentials but the first call that is made to the Realtime Database results in a PERMISSION_DENIED error. The current workaround that I have found for this is to call firebase.auth() immediately after calling firebase.initializeApp and that seems to kick start authentication to work correctly. This bug only happens in a worker context. Previously, in v8 we were able to just call firebase.initializeApp and authentication would automatically link to the authentication of the client. Thank you for your time!

Here is the error that I am hitting:

Steps and code to reproduce issue

In a worker include these imports (firebase v10.6.0):

import firebase from 'firebase/compat/app';
import 'firebase/compat/database';
import 'firebase/compat/auth';

then call firebase.initializeApp(credentials_go_here) followed by an update
to the RTDB (example: await firebase.database().ref('test/path/here').update({'test': 'testing'});

This should result in the PERMISSION_DENIED error

[DellaBitta]

Hi @jdcoldsmith,

It could be the case that while the Auth SDK has been initialized automatically when using RTDB, but the user account hasn't officially be read from persistence and signed in to the Auth SDK before your utilization of the database SDK. Therefore the database request is being blocked because there's no authorized user yet.

Could you try waiting for the promise returned by AuthStateReady() is complete, and then checking the current user is valid before accessing the database operations? Thanks!

[google-oss-bot]

Hey @jdcoldsmith. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

[google-oss-bot]

Since there haven't been any recent updates here, I am going to close this issue.

@jdcoldsmith if you're still experiencing this problem and want to continue the discussion just leave a comment here and we are happy to re-open this.