I made an extension for Google Docs using Apps Script. It worked fine during testing but now it’s not working right. I put it on our company’s internal Google Marketplace after getting the okay from my boss. But now when I try to use it, the button is all grayed out and I can’t click it.
I made sure to add all the right permissions in the code. Here’s what I put in the 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 this is happening? It’s really weird because it was working before I put it on the Marketplace. Now it’s just sitting there looking sad and gray. Has anyone else run into this problem before? I’m kind of stuck and don’t know what to do next. Any help would be awesome!
hey mike, had similar issue b4. chek ur deployment settings? sumtimes when u publish, it messes w/ permissions. try redeploying as new version & make sure ‘execute as’ is set to u or user accessing app. also double-check marketplace listing 4 any weird settings. gl!
Have you verified the extension’s visibility settings in the Google Workspace Marketplace SDK? Sometimes, these can impact functionality post-deployment. Also, check if there are any error messages in the browser console when you try to use the extension. This could provide valuable clues.
Another aspect to consider is whether your company’s domain-wide installation policies might be affecting the extension. In some cases, admin approval might be required even for internal marketplace apps.
If you’re still stuck, you might want to try creating a new test deployment with slightly modified code. This could help isolate whether the issue is with the deployment process or the code itself. Remember to clear your browser cache before testing each new version.
I’ve encountered this issue before, and it can be frustrating. One thing to consider is whether your company’s IT policies might be interfering with the extension. Sometimes, corporate security measures can block or restrict custom add-ons, even if they’re on the internal marketplace.
Have you tried reaching out to your IT department? They might need to whitelist the extension or adjust some security settings to allow it to function properly. Additionally, it’s worth checking if other colleagues can use the extension or if it’s just affecting your account.
Another potential solution is to review the OAuth consent screen settings in your Google Cloud project. Sometimes, the scopes need to be re-authorized after deployment. You might want to try removing and re-adding the extension to see if that triggers the necessary permissions prompt.
If none of these work, consider creating a test deployment with a different version number and see if that functions correctly. This could help isolate whether it’s a deployment issue or something more systemic.