I’m trying to deploy my Google Docs add-on but running into a frustrating issue.
I’ve been following the standard deployment process for Google Docs add-ons. Everything goes smoothly until I reach the Google Apps Marketplace SDK configuration step.
When I input my script project key (which I copied from the file menu under project properties), I get this error message: ‘Project Key is not associated with the current project.’
I already checked the common solution where people accidentally create their project through Google Developers Console instead of using the Resources menu and Advanced Google Services option. That’s not my issue since I followed the correct workflow.
Has anyone else encountered this specific error during add-on deployment? I’m not sure what else could be causing the project key mismatch.
Any suggestions or troubleshooting steps would be really helpful. Thanks in advance!
This usually happens when your script project and developer console project don’t match up. I ran into this exact issue when deploying my own add-on - turned out to be a permissions problem. First, make sure you’re logged into the same Google account in both Apps Script and Developer Console. Switching accounts often breaks this connection. Also check that your script is published as a web app or API executable - the marketplace SDK needs this setup first. If it’s still not working, grab a fresh project key from your Apps Script properties and paste it right away. Don’t copy anything else in between or it might mess up.
Had this same error 6 months ago. Clear your browser cache and cookies for both Google Apps Script and Developer Console, then start over. There’s usually cached auth data messing up the project association even when everything looks right. After clearing everything, re-authenticate both services and the project key should work right away. Also check you’re using the current project key format - Google changed their structure recently and old keys from existing projects sometimes won’t validate in marketplace config. Took me about 15 minutes once I cleared the cache.
refresh the script editor page and grab a new project key. the key goes stale when ur working on other stuff. also check ur logged into the same google account in both tabs - sounds obvious but it happens all the time.
Check if you’ve enabled the Google Workspace Marketplace API in your Cloud Console project. This trips up tons of people - you have to manually activate it before project key association works. Head to Cloud Console > APIs & Services, search for Google Workspace Marketplace API, and enable it if it’s not already on. Give it 10-15 minutes to propagate across Google’s systems. Had this exact problem last year and enabling that API fixed the project key mismatch right away. The error’s misleading - makes you think the key’s wrong when it’s really just an API permissions thing.
omg, i had that too! make sure ur script project is properly saved and linked. the connection can go a bit wonky sometimes. i had to create a new project to fix it. good luck!
Been there with Google Apps Script deployment headaches. The manual linking process is painful and error prone.
Your script project probably got disconnected from the developer console project somewhere along the way. Google’s infrastructure for this stuff is honestly pretty clunky.
Instead of wrestling with manual configurations and project key matching, I’d automate the whole Google Docs integration differently. You can build the same functionality using automation workflows that connect directly to Google Docs API without dealing with add-on deployment.
I switched to this approach after getting burned by similar deployment issues multiple times. Now I create Google Docs automations that work reliably without the marketplace SDK hassles. The automation handles document creation, editing, sharing - basically everything you’d want in an add-on but with way less friction.
No more project key mismatches or broken links between different Google consoles. Just straightforward API connections that actually work.
Check out how to set this up: https://latenode.com