Most of the comments I get on this site have to do with someone trying something I’ve written about that isn’t working for them. In most cases, error messages can be your friends since they can point to the particular place your script failed and give you additional insight into why it failed.
This post will describe some of the ways you can use the built-in tools of the Google Apps Script environment to debug or troubleshoot your own scripts. My goal here is start from the easiest to implement and work towards more difficult, but more efficient, methods of debugging.
Source: Debugging in Google Apps Script – Jeff Everhart
This article will highlight how you have to be careful about settings when you make some content available publicly, like Groups or Drive file.
The original article describe how an external person of the domain can subscribe to your Slack company channel by using a Google Groups that is publicly accessible. Stéphane Giron’s article helps answer the question – how to prevent and how to identify if some groups are concerned.
Source: GGvulnz — How to check your domain and groups settings
This is an overview of the various techniques and best practices I have evolved in developing Google Apps Scripts over the years. Of course Google have got a few suggestions of their own, and there are plenty of more general …
This includes some good design pattern considerations for Apps Script projects as well as links to testing libraries, boilerplate frameworks, and extensions that help manage Apps Script work.
Source: Google Apps Script Development – Best Practices – Andrew Roberts
I’m a public school teacher writing Apps Script projects to manage documentation and to make life easier in general. You can read more on my blog, blog.ohheybrian.com or follow me on Twitter, @bennettscience.
I stumbled upon this particular oddity a few weeks ago when a client asked me to resolve an issue.
Nice highlight from Dimu Designs, the source thread is open for other ‘gotchas’.
Source: The more you know! – Google Groups