共享Google表格后按钮绑定脚本无法运行，onEdit()功能正常求助

Hey there! It’s super common to hit permission or context issues when sharing bound Google Scripts with multiple editors—especially when you’re new to the platform. Let’s break down why your button-triggered function is failing while onEdit() works, and how to fix it:

First, Get the Actual Error Message #

The generic "Script experienced an error" message doesn’t tell you much. Have your collaborators do this to see details:

• Open the shared spreadsheet
• Go to Extensions > Apps Script to open the script editor
• Find the function tied to your button, click the run button ▶️ next to it
• Any error (like permission issues, missing resources, or logic bugs) will show up here. This is the fastest way to narrow down the problem.

Most Likely Causes & Fixes #

1. Permission Mismatch Between onEdit() and Button Functions #

onEdit() is a simple trigger—it runs automatically under the current user’s permissions, with strict limits (no access to external services, no long runtime). But button-triggered functions run as "regular" functions, which may require OAuth authorization that your collaborators haven’t granted yet.

• Fix: Have each editor open the script editor and run the button function once. They’ll see a prompt to authorize the script—click "Advanced" > "Go to [Script Name]" (since it’s un-verified) and complete the authorization flow. After that, the button should work for them.

2. Your Function Uses Resources Only You Can Access #

If your script references something specific to your account (like a hidden sheet only you have permission to view, a named range that doesn’t exist for others, or a personal Google Drive file), collaborators will get errors when trying to access those resources.

• Fix: Audit your code for any hardcoded references (e.g., getSheetByName("My Hidden Sheet")). Make sure all sheets/ranges your script uses are accessible to all editors, or add checks to handle missing resources gracefully.

3. Overly Broad Permissions or Cross-Spreadsheet Access #

If your script uses SpreadsheetApp.openById() to access a different spreadsheet (not the one it’s bound to), that requires extra permissions collaborators might not have. Stick to context-specific methods for the bound sheet to avoid this:

• Instead of openById("123..."), use SpreadsheetApp.getActiveSpreadsheet() to reference the current sheet
• Use getActiveSheet() or getSheetByName() with sheet names all editors can see

4. Runtime or Logic Bugs #

Sometimes the error is just a plain old bug in your code that only surfaces when other users run it (e.g., relying on your active cell position, or assuming a row has data that’s missing for others).

• Fix: Test the script with another account to replicate the error, then debug line-by-line in the script editor using the "Debug" button to step through the code.

内容的提问来源于stack exchange，提问作者MBT