Marcus Gallegos

Experiencing this on Chrome and Brave. See console error: 

@alexluong Hi, do you need help maintaining this project? Would love to get this plugin back on track for the community. :)

@alexluong Sure, no problem! I've been looking for a project to work on and I can see myself using this one a lot. From what I gather in my own...

@alexluong Oof, okay it seems we have some real investigation to do then. Let me get a public repo to you so the issue can be recreated. Sound good?

I have added a comment to an existing issue since it seems to be the same problem. I added a link to the repository there. :) #31 #

I have replicated this issue on a project I'm working on. You can find the [repo here](https://github.com/Marcusg62/inhouse-marketing-site). Most of the firebase stuff is in src/firebase/firebaseService.tsx It works fine when running...

I'm assuming this is what you mean. https://github.com/Marcusg62/inhouse-marketing-site/blob/7df3aa47a2e58454db5bc3623f04a408d562a089/inhouse-marketing/src/firebase/firebaseService.tsx#L97-L103 Done. I get the same error when trying to build. I've pushed to master if you'd like to take a look.

@alexluong I recommend archiving this repo.

Look at this [stack overflow question](https://stackoverflow.com/questions/52030741/node-firebase-oncall-asynchronous-function-return). By definition all callback functions are async so you would have to force your code to wait for the promise to resolve to send...

Thanks for doing this, I'm experiencing this issue at my org - much needed!