Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Firebase error #9

Open
thunderwilson opened this issue Jun 22, 2023 · 5 comments
Open

Firebase error #9

thunderwilson opened this issue Jun 22, 2023 · 5 comments

Comments

@thunderwilson
Copy link

Followed instructions correctly as per this repo, and corresponding blog post.

When running locally I get the following error:

image

I will also note that following the instructions directly did not work. If you follow the instructions, when you get to the secrets section, you can open the GCP secrets manager, and add secrets, but you cannot refresh the list and see your secret. You can only do that after you have enables Rowy cloud run.

After troubleshooting this a few times I made sure I enabled Rowy cloud run first after creating the project in rowy, then I added the table template as per the instructions.

@thunderwilson
Copy link
Author

After I try log in with a Google account, I get this error also:

image

@rodgetech
Copy link
Contributor

Hi @thunderwilson, sorry for the late reply. I will investigate this issue with tableEnv and get back to you. Thanks for raising this issue.

@rodgetech
Copy link
Contributor

Hey @thunderwilson, can you please verify that tableEnv was actually added to you're firestore database during the template setup. You should be able to check this in the firebase console of your project. If you went with the default name for table this should be the path you can enter in firestore: /_rowy_/settings/schema/microSaaSProfiles

tableEnv

@thunderwilson
Copy link
Author

Yes,. everything looks correct here.

image

@rodgetech
Copy link
Contributor

Oh I see, yes that looks correct. I seem to be unable to reproduce this issue so my only hunch is that maybe you're not setting the NEXT_PUBLIC_PROFILES_TABLE_ID environment variable correctly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants