Assigned
Status Update
Comments
sh...@google.com <sh...@google.com> #2
Hello,
Thank you for the details. This has been forwarded internally.
Best regards
ha...@gmail.com <ha...@gmail.com> #3
Hi,
Same here. We have a set-up running which is far below the quota, but on certain occasions it fails when accessing a document with the same error message: "service spreadsheets timed out while accessing document with id".
While normally happening only once in a while, for the last weekend it has been happening on every occasion of it running, which is every hour, so for the last 40+ times of it running it has thrown an error.
For me it fails most often on this row:
spreadsheetApp.openById("...").getSheetByName("name").getRange(1,1, sheet.getLastRow().createTextFinder("...").matchCase(false).findNext();
It would be very helpful if this could be investigated!
Thanks.
Same here. We have a set-up running which is far below the quota, but on certain occasions it fails when accessing a document with the same error message: "service spreadsheets timed out while accessing document with id".
While normally happening only once in a while, for the last weekend it has been happening on every occasion of it running, which is every hour, so for the last 40+ times of it running it has thrown an error.
For me it fails most often on this row:
spreadsheetApp.openById("...").getSheetByName("name").getRange(1,1, sheet.getLastRow().createTextFinder("...").matchCase(false).findNext();
It would be very helpful if this could be investigated!
Thanks.
ha...@gmail.com <ha...@gmail.com> #4
I think this is a V8 Runtime issue. I disabled V8 Runtime early last week and I haven't had this issue since. V8 is technically still in BETA and I've posted a seperate bug previously regarding specifically the V8 Runtime in which Google was able to replicate and is currently working on a fix
EDIT: The error happened again this morning (May 22nd) and the code ran on the previous runtime enviornment. So this bug is not specific to the V8 runtime enviornment
EDIT: The error happened again this morning (May 22nd) and the code ran on the previous runtime enviornment. So this bug is not specific to the V8 runtime enviornment
sh...@google.com <sh...@google.com> #5
Any update on this? This has started to become a daily issue for my organization..
Description
Component used: androidx, viewpager2, bottomsheet Version used: 1.2.0-beta01 or earlier Devices/Android versions reproduced on: Pixel 5
This is a show-stopper for my app. Please advise! Just run the attached sample. It clearly demonstrates the issue. The
RecyclerView
loads all items that would have been visible if the bottomsheet was fully expanded. It makes no sense. Or if it does, please show me how to disable this behavior. I don't want to load any item until the bottomsheet is being dragged/expanded. I can accept any delay at that point.By now, I have tried pretty much everything. If the adapter is non-empty upon view initialization the views will simply be loaded and drawn. Fixing this means adding/removing adapter items which seems like a complicated hack.