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

courses/flutter-firebase/firestore-data-model/ #836

Open
utterances-bot opened this issue Jul 3, 2022 · 7 comments
Open

courses/flutter-firebase/firestore-data-model/ #836

utterances-bot opened this issue Jul 3, 2022 · 7 comments

Comments

@utterances-bot
Copy link

Database Model

Model relationships between quiz entities in Firestore

https://fireship.io/courses/flutter-firebase/firestore-fetch/

Copy link

I'm not seeing the "generate private key" button on the firebase service accounts settings page. I have seen screnshots where the button should be, but it's just not there... how to get the credentials.json file now?

Copy link

generate private key is in project settings -> service accounts -> firebase admin sdk, after that you need to rename the file to credentials.json

Copy link

If you can't get his database uploader working, due to deprecated warnings, i created a branch that works: https://github.com/matt-sdc/fireship-quizapp-data/tree/bugfix-dependency-fix

Copy link

gael1130 commented Aug 2, 2022

It wasn't working for me. I ended up finding this answer ==> grpc/grpc-node#1460 (comment)
So I downloaded nvm (https://github.com/nvm-sh/nvm#installing-and-updating).
Then did

nvm install 12.0
npm install

The project worked for node v12 but not for my original version (17)

Copy link

So lost with this entire class... Getting UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 48) with node version 12

Copy link

Jitan commented Sep 25, 2022

Using NVM to switch to version v12.9.0 worked for me. Remember to delete node_modules and re-run npm install after switching.

@Lukmauu
Copy link

Lukmauu commented Jul 20, 2023

As in 2023

I had to run:

npm install @grpc/grpc-js
npm audit fix --force

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

8 participants