Apps Script Extension for Google Docs not functioning after official installation

Other Questions Google docs
1

I made an Apps Script Extension for Google Docs and got permission from my admin to put it on our internal Google Marketplace. It worked fine when I was testing it. But now that I’ve installed it through the Marketplace it’s all grayed out and I can’t use it.

I made sure to include these OAuth scopes in my appsscript.json file:

\"oauthScopes\": [
  \"https://www.googleapis.com/auth/documents\",
  \"https://www.googleapis.com/auth/script.external_request\",
  \"https://www.googleapis.com/auth/script.container.ui\"
],

Does anyone know why my extension isn’t working now? It’s frustrating because it was fine during development. Any ideas on how to fix this?

2

Have you tried uninstalling and reinstalling the extension? Sometimes that can resolve issues after deployment to the Marketplace. Also, double-check that your admin actually approved all the OAuth scopes you requested. I’ve seen cases where admins only partially approve scopes, which can cause extensions to malfunction.\n\nAnother thing to look into is version mismatch. Make sure the version in your Marketplace listing matches your latest deployment. If they’re out of sync, it could explain the grayed-out UI.\n\nLastly, try testing the extension with a different Google account in your organization. If it works for them but not you, it might be a permissions issue specific to your account. Hope this helps troubleshoot the problem!

3

I’ve run into similar issues with Apps Script extensions before. One thing that often gets overlooked is making sure your manifest file (appsscript.json) is up to date in the Marketplace version. Sometimes when you make changes locally, they don’t automatically sync to the published version.

Try going to your Google Cloud Console project associated with the extension. Check if there are any discrepancies between the OAuth scopes listed there and in your local manifest. I’ve had cases where I needed to manually update the scopes in the Cloud Console to match my local changes.

Also, have you tested the extension with a non-admin account? There could be some weird permission quirks happening if you developed it with elevated privileges. If it works for regular users but not admins, you might need to adjust how you’re handling authorization in your code.

Lastly, don’t forget to check your browser’s developer console for any JavaScript errors. Sometimes the UI gets grayed out if there’s an uncaught exception when the extension tries to initialize. Hope this helps you track down the issue!

4

yo, have u checked your browser’s console for any error messages? sometimes that can give u clues about whats going wrong. also, maybe try clearing ur browser cache and cookies. that fixed a similar issue for me once.

if none of that works, u might wanna reach out to ur admin. they might need to tweak some settings on their end to get it working.