High Mobile Network and Wifi Usage - Pixel 9 Pro [371227619]

Obsolete

Bug

Status Update

No update yet.

Description

vi...@gmail.com

created issue #1

Oct 3, 2024 10:42PM

To avoid the possibility of sharing private information, please share bugreports and screenshots from Google Drive. Share files with android-bugreport@google.com and include only Google drive links in your bug. If attaching bug reports or other sensitive data directly to issues, please mark the attachment(s) as “Restricted (

https://developers.google.com/issue-tracker/concepts/restricted-content)” when creating a bug or adding a comment. Restricting or deleting your comment or attachment can also be done using the overflow menu after submitting.

Disclaimer:
Please note, by submitting this bug report, you acknowledge that Google may use information included in the bug report to diagnose technical issues and to improve our products and services, in accordance with our Privacy Policy (

https://policies.google.com/privacy), and you agree that we may share it with engineering partners potentially impacted by your issue.

Bug reports include personal information logged on your device or by apps, such as:
File names
Installed apps and usage
Email addresses of the profiles on the device
Device identifiers, such as phone number
Web history information, including URLs / URIs
Location information, including limited location history
Network information, such as IP/SSID/MAC addresses and saved or scanned APNs
System or device information, such as memory and processes

bugreport-caiman-AD1A.240905.004-2024-10-03-18-18-32.zip -

https://drive.google.com/open?id=1DrJ3Mb9afxwJH_9RGntoO3cdocHN8V4W

deleted

Restricted

0 B

Comments

vi...@gmail.com <vi...@gmail.com> #2Oct 4, 2024 12:12AM

Hello,

Thank you for creating this issue.

I could not reproduce this behaviour. Time-based triggers are running even after following the steps you specified.

From the screenshots you shared, it looks like there are two functions in your project that have the same name. This might be the reason you are getting the behaviour you expect. Are you sure that's not the case? Can you share all the code you're using (if you haven't done it already) so that I can try to reproduce this.

Kind regards.

ra...@google.com <ra...@google.com> #3Oct 4, 2024 03:46AM

Status: Won't Fix (Obsolete)

It does look like it's impossible to reproduce with a simple use case that I specified.
We have a huge project and it would be impossible to put all the code here. Right now we are working on removing duplicate function names (even though none of them is called from a trigger) to see if it fixes it.
But in our project, the described steps stop the trigger execution in 100% of cases.

mi...@gmail.com <mi...@gmail.com> #4Oct 20, 2024 10:38AM

Hello,

Please remove all the duplicate function names in your project and see if the problem persists.

Kind regards.

Issue 371227619

Description

Issue summary

Comments

vi...@gmail.com <vi...@gmail.com> #2Oct 4, 2024 12:12AM

ra...@google.com <ra...@google.com> #3Oct 4, 2024 03:46AM

mi...@gmail.com <mi...@gmail.com> #4Oct 20, 2024 10:38AM

Add comment

Issue metadata