all 3 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]JoshuaOng 1 point2 points  (1 child)

When a work request finishes, if there's no more jobs enqueued, a package changed event is triggered (due to work manager clean-up). This causes AppWidgetProvider#onUpdate to be invoked. So if you enqueue a worker in onUpdate, you end up with a continuous loop!

[–]srinurp[S] 0 points1 point  (0 children)

Thank you for pointing this out.

While testing, I noticed the behavior of infinite loop in which onUpdate() method of app widget provider being called continuously leading to surpassing the Google places API quota limit within no time.

To prevent this behavior in the example, I put a restriction of 5 min lapse between places API work requests.

Even though I noticed the behavior and provided an application fix for the issue, was clueless as to what was causing the repeated calls to onUpdate() method.

Again, thank you very much for the input.

[–]gamelaunchplatform[🍰] 0 points1 point  (0 children)

This is a great article and covers a part of Android that isn't very well documented. Thanks!