Assigned
Status Update
No update yet.
Comments
jp...@google.com
Solved for now by adding @SuppressWarnings. We'll need to revisit if this pops up again.
Ideas include:
- Whack-a-mole overrides via NullAway Library Models
- Have an custom extract_only=true on the upstream aar targets so that they cannot be accidentally used, and then use the extracted classes.jar files only in the errorprone classpath.
bl...@google.com
Automated by Blunderbuss job workspace-devrel-public-issue-tracker-blunderbuss-autoassigner for config assign for component 191640.
Description
I have discovered a bug in Google Apps Script related to account switching. When a user is logged into multiple Google accounts and tries to switch accounts in the script editor or execution environment, the account does not change as expected. Instead, the script continues running under the original account, which can cause access issues.
Steps to Reproduce: Log into multiple Google accounts in the same browser session.
Open the Google Apps Script editor under one account.
Attempt to switch to another account.
Notice that the account does not actually switch, and the script runs under the original account.
Proposed Solution: I believe this issue could be fixed using an "authorize user 0 or 1" method, ensuring that the script properly recognizes and switches to the intended account.
Please let me know if any additional information is needed. I appreciate your time and consideration in resolving this issue.
Best regards, Connor Gentile-DePaul