Assigned
Status Update
No update yet.
Comments
ho...@gmail.com
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
Android build
Which Android build are you using? (e.g. UQ1A.240205.002)
Device used
Which device did you use to reproduce this issue?
Screen Record of the Issue
Please capture screen record or video of the issue using following steps:
adb shell screenrecord /sdcard/video.mp4
Subsequently use following command to pull the recorded file:
adb pull /sdcard/video.mp4
Attach the file to this issue.
Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:https://developer.android.com/studio/debug/bug-report#bugreportdevice
Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.
Note: Please upload the bug report and screenrecord to google drive and share the folder to android-bugreport@google.com, then share the link here.
Android build
Which Android build are you using? (e.g. UQ1A.240205.002)
Device used
Which device did you use to reproduce this issue?
Screen Record of the Issue
Please capture screen record or video of the issue using following steps:
adb shell screenrecord /sdcard/video.mp4
Subsequently use following command to pull the recorded file:
adb pull /sdcard/video.mp4
Attach the file to this issue.
Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:
Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.
Note: Please upload the bug report and screenrecord to google drive and share the folder to android-bugreport@google.com, then share the link here.
ak...@mixedanalytics.com
ha...@gmail.com
Please provide the requested information to proceed further. Unfortunately the issue will be closed within 7 days if there is no further update.
pl...@gmail.com
We are closing this issue since we didn't receive a response. If you are still facing this problem, please open a new issue and add the relevant information along with reference to this issue.
ad...@gmail.com
Determined that if one times the screenshot correctly, the time can be
captured. Time flashes blank/stopwatch time at 1 hertz.
OK to close.
Corbet
On Thu, Nov 7, 2024, 11:59 PM <buganizer-system@google.com> wrote:
captured. Time flashes blank/stopwatch time at 1 hertz.
OK to close.
Corbet
On Thu, Nov 7, 2024, 11:59 PM <buganizer-system@google.com> wrote:
an...@gscript.pro
Please FIX it !
dr...@clinicaunivitta.com.br
Please FIX IT!
al...@alicekeeler.com
I am having the same issue.
jp...@google.com
sa...@tscfo.com
Hi! I'm experiencing this issue too so I suppose the bug has not been addressed by google yet. Is there any update/workaround or potential solution anyone has come up with? This makes building apps with google app script unreliable and therefore not an option anymore...
ja...@checksheet.app
I've seen a spike in occurrences of this issues, it seems to mainly be affecting time based triggers which are crucial for my add-on.
Under what circumstances should we expect a time based trigger to be disabled?
ja...@checksheet.app
Can we get an update on this? I'm seeing more and more users having their time based triggers which is severely affecting my application.
ba...@gmail.com
Yes, we are also seeing this issue and would like to see it resolved. It is a critical failure.
ta...@gmail.com
Here's another similar issue from 2019, and it doesn't look the AppScript team is even looking at it: https://issuetracker.google.com/issues/142405165
Description
-----------------------------------------------------------------------------------------------------------------------------
A short description of the issue:
When I go to Edit Current Project Triggers in my Sheets add-on script editor, I can see several triggers are showing as disabled. Some of these were "one-time" executions, some are form on submit triggers.
The code functions perfectly in the original script container, that is, the error is only present for users of the add-on.
Sometimes the triggers simply disappear, but in this case they're still in the list but showing up as disabled. I have no way of viewing the disabled reason, because I don't have access to the script. Even when I share one of the Sheets with the owner of the original project, I still can't see the disabled reason (although it's hard to know which trigger belongs to which script).
A small code sample that reliably reproduces the issue. The sample should run as-is or with minimal setup, without external dependencies.
This issue can't be reliably reproduced.
What steps will reproduce the problem?
1. Install the Benko Board sheets add-on
2. Wait
3. Triggers will stop working
What is the expected output? What do you see instead? If you see error messages, please provide them.
Expected: reliable and functioning triggers
Saw: triggers both disappearing and being marked as disabled