-
-
Notifications
You must be signed in to change notification settings - Fork 390
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
Creating a spreadsheet document with the JWT causes an error #701
Closed
Ivokato opened this issue
Aug 23, 2024
· 3 comments
· May be fixed by Pablo11111544545/moneyman#1, WontonSam/website#46 or WontonSam/website#59
Closed
Creating a spreadsheet document with the JWT causes an error #701
Ivokato opened this issue
Aug 23, 2024
· 3 comments
· May be fixed by Pablo11111544545/moneyman#1, WontonSam/website#46 or WontonSam/website#59
Comments
I don't have much to offer, but curiously, have you tried |
I met same issue with official documentation code |
fix incoming shortly! |
junedomingo
added a commit
to junedomingo/node-google-spreadsheet
that referenced
this issue
Sep 23, 2024
* main: wiring up github action to dmno chore: release v4.1.4 add dmno and remove/encrypt test-related secrets, swap jest for vitest fix(updateProperties): getFieldMask ignore gridProperties (theoephraim#674) chore: release v4.1.3 fix bugs introduced by PRs update axios, fix new google-auth-library issue, fixes theoephraim#701 theoephraim#700 Read headers in batch on getRows() (theoephraim#693) Update authentication.md allow CI manual reruns Update FUNDING.yml use correct type in docs # Conflicts: # .gitignore # pnpm-lock.yaml
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After reinstalling my node modules I got this error:
Cannot use api key only to create a new spreadsheet - it is only usable for read-only access of public docs
My bare minimum code taken from the official documentation is failing:
I figured out that the error is thrown because there is a key called "apiKey" in the JWT. Downgrading the google-auth-library to 9.13.0 has solved the issue for me so I would recommend either fixing the dependency or updating the check that throws the error
The text was updated successfully, but these errors were encountered: