Infeasible
Status Update
Comments
jp...@google.com <jp...@google.com> #2
The flow of the wizard is really meant for the key to be used for signing. In fact, if you want to just create a key for code transparency you have to start a flow (signing an APK/Bundle) and then back out of it/cancel after you created the key.
To properly support this, we should also allow you to start a wizard that is just creating a key, and nothing else.
bl...@google.com <bl...@google.com> #3
Thanks for this feature request. The "Generate Signed Bundle / APK" flow is only meant to generate keys for APK or AAB signing. We'll plan to add a warning to the flow to clarify that.
jp...@google.com <jp...@google.com> #4
Likely related to the contents of the spreadsheet.
Description
Before opening a new issue, please search for other related issues , click the ★ to subscribe to updates, and click
+1
to vote.Description
TLDR: Timeout on openById() for specific sheet & clones since 8:30am on March 23rd. Other 2 work fine.
I’ve been using a Google Sheets file with an Apps Script function on a 10-minute trigger for years without issues. However, around 8:30am PST on March 23rd, this function suddenly stopped working and hasn't been completed a single time since, even though 2 other similar spreadsheets continue to run flawlessly with exact same function.
The problem appears to occur during a call to SpreadsheetApp.openById() which seems to be timing out. Even copies of the affected spreadsheet inherit the issue, suggesting that it and its duplicates might be hosted in the same datacenter.
If any member of the Google team is reading this, I’d greatly appreciate your help investigating the matter, as this spreadsheet is critical to my workflow.
Affected Sheet ID: 1g1tb6DreV2yzhWSqZBiHn28MCZjxcvPv8o-b_au8QTk
Code
Output
In the full code version, I get:
In the simplified version, as per the code above, I get:
Steps