Google Apps Script showing verification warning when accessing my own spreadsheet

Other Questions Google Sheets
1

I created a simple Google Apps Script to work with my personal spreadsheet but I keep getting a verification warning every time I try to run it. The script is stored in the same spreadsheet file and I’m just trying to read data from it. I thought scripts should work automatically when they’re part of your own Google Sheets file.

I already turned on the Sheets API in the Advanced Services and also in the Google Cloud Console. Do I really need to go through app verification just to run a script on my own data?

This is the basic function that triggers the warning:

function findLastDataRow(){
  const workbook = SpreadsheetApp.getActiveSpreadsheet();
  const dataSheet = workbook.getSheetByName('settings');
  return dataSheet.getLastRow();
}

Is there a way to skip this verification step for personal use scripts?

2

Had the same issue last month - turned out to be an execution environment thing. Your script looks fine, but Google flags container-bound scripts if they see weird activity patterns or you’ve got other scripts running with broader permissions. The verification warning also pops up if your account’s created scripts before that needed sensitive scopes, even when this one doesn’t. Try making a fresh spreadsheet with a new script container and test the same function. If it runs without warnings, something in your current setup’s triggering the security check. Also check if you accidentally enabled extra APIs or services that might be expanding permissions beyond what your simple function needs.

3

This verification warning can occur even for basic spreadsheet functions if certain security settings are enabled or if previous scripts were created with broader permissions. Your function should operate correctly as it only interacts with the active spreadsheet. I suggest removing the script’s authorization entirely—go to your Google Account settings, navigate to Apps with account access, find your script project, and delete the permissions. Then, try running the script again and complete the authorization process anew. Google’s security measures can become confused due to remnants of old script versions or other projects. This verification warning may also arise if you are using a work or school account that has additional security policies in place.

4

that’s odd, right? basic scripts rly shouldn’t trigger those warnings. maybe double check if other codes are runing? sometimes things get mixed with oauth scopes. try making a new script file and just test that function alone.