API Developer Key invalid
This seemed to just start coming up did anything change recently with the new versions? Nothing in the logs.
GitHub Issue
https://github.com/baptisteArno/typebot.io/issues/1163
GitHub
The API developer key is invalid. · Issue #1163 · baptisteArno/type...
This just started to pop up I was not having any issues. May be related to cloudron but im not sure its such an odd error. Nothing in the logs.
78 Replies
Now the Google Sheets block uses the Drive Picker API to be more compliant with privacy
See the breaking changes here: https://github.com/baptisteArno/typebot.io/releases/tag/v2.21.0
GitHub
Release v2.21.0 · baptisteArno/typebot.io
Breaking changes
The Google Sheets block config was updated and its configuration changed.
The Google Picker API needs to be enabled in the Google Cloud console. You also need to enable it in your...
It worked I missed adding new API
Unknown User•15mo ago
Message Not Public
Sign In & Join Server To View
@Baptiste can you guide on this please.
I don't think you can use localhoat to get to googles API. You may have to set up actual domains. I could be wrong though as I've never tested running locally.
I dont see any such reported issues on community
GitHub
The API developer key is invalid. · Issue #1163 · baptisteArno/type...
This just started to pop up I was not having any issues. May be related to cloudron but im not sure its such an odd error. Nothing in the logs.
We have this enabled already but still having this problem
Check: https://docs.typebot.io/self-hosting/configuration#google-auth-sheets-fonts
Make sure you have all 3 variables set
Hello @CptPlastic and @MasterIBM, sorry to make an old post coming back, but im having the same issue
- Picker API enabled
- Sheet API enabled
- All 3 variables filled (and valid, because i also use the Google Auth with success)
I successfuly add the account, but when i need to select the sheet, i got the "The API developer key is invalid."
Did you try regenerating your key
Yes, generated 3 differents keys
Mine expired before and I ended up seeing this.
Hmm I’m not sitting in front of my computer but when I am I’ll look at how my setup is and screenshot it for you.
It’s been awhile since I had to touch that part of my configuration
Thanks 😄
Where do you see this ? Im on the credentials page but my key isnt restricted to anything
Then should be good to go
Here is my env setup
Yep i got everything right on that file, but still the error message
If you have all three permissions set it should work. Are you selfhosting the latest version of the main branch?
One other thing i thought of was the URL you have set is that an Actual domain? I know the have to be FQDN to work right with googles API
Set where ?
The key isnt even restricted for now
GitHub
The API developer key is invalid. · Issue #1163 · baptisteArno/type...
This just started to pop up I was not having any issues. May be related to cloudron but im not sure its such an odd error. Nothing in the logs.
google picker api
It's enabled yes
whats it say when you click manage
That it's enabled and usable by the key that i use on typebot
should work if thats the key and your domain is fully qualified
Google Sheets API
Google Picker API
Google Drive API
you might check to make sure all those are enabled
Sadly they are :/
can you do me a fav and screenshot your .env file you can scrub the keys I just want to see something
Yep
hmm looks fine spaces are odd but should not matter
yep, im desesperate :/
where do you host this at?
An OVH dedicated server
and are you able to console into the container?
Yep
If you mean checking the logs, there is nothing on it
no i mean like console into the running container and go to this path
root@92c249e7-5c52-40a4-af02-5f4c24d4ed8c:/app/code/builder/apps/builder#
ls
public
should see that folder
node_modules package.json public server.js src
yepgo in it look for _ENV.json
__ENV.js you mean ?
yep
window.__ENV = {"NEXT_PUBLIC_GOOGLE_API_KEY":"XXX","NEXT_PUBLIC_VIEWER_URL":"https://candidature.XXX.io"}but it shows your key right
Yep
damn
And im on the latest
the only thing I can think of is google bnlocking you for some reason
im on the same version also
Well, the Oauth work well, i can connect through google on the builder
So i don't think that google did blocked me
so when you select new account for the sheets block do you see
Yes
That way
After i authenticate
than it says something like
com already has some access
See the 4 services that nsnmindlabs.com has some access to.
something like that
Mmh no it simply validate the connexion and redirect me on the builder
When i click on "accept"
hmmmmmmm
thats where the hickup is then
that key is not passing any permissions
at least it would appear that way
Well, as you can see here, when i go to the google profile; i can see that my app do have the permissions for it on my account
Its not in english so its hard for me to read
My bad
It says "Your app has somes right on your google account"
I feel like this is something silly with the way your auth is setup
And then specify the google dreive read edit and delete, and the same thing for google sheet
what rights are they
- View your profile information
- View, modify, create and delete all your Google Sheets spreadsheets
- View, modify, create and delete only the specific Google Drive files you use with this application
but when you select a sheet its invalid
you have a google sheet in your googledrive right
Yep
im at a loss then without actually logging in and seeing your set up im not sure what else to try
If you are available i can screenshare you, but i don't want to take any more of your time
it should just simply work from what you shown
ok one sec
ok ready whenever you are
Let's go
Oh there is no vocal channels here
@Mathitux glad we fixed that issue yesterday. Here is some information about scopes.
https://developers.google.com/identity/protocols/oauth2/scopes
Looks like scopes don't get added by default anymore to consent screens so I can see people running into this more.
Google for Developers
OAuth 2.0 Scopes for Google APIs | Authorization | Google for D...
Yep, clearly
Thanks again for your time on this