1366045 - Consider better approaches to scheduling java telemetry uploads

Status: RESOLVED INCOMPLETE

(Firefox for Android Graveyard :: Metrics, enhancement, P5)

Description

[:Grisha Kruglov]

Currently uploads of telemetry pings will get kicked off only in response to a new ping.

For sync ping (see Bug 1308337) this might mean that if a user either:
- doesn't sync for a long time, or
- disables sync altogether,

we might never upload whatever pings they currently had in the queue.

Note that this isn't a problem for the core ping, since those are generated regularly and uploaded right away.

One solution is to make use of the AlarmManager, and schedule uploads in the future. This comes with the drawback of having to deal with _not_ scheduling ourselves into the future when there obviously isn't anything to upload.

Another partial solution, and likely what we'd want to have regardless, is to upload any pings whenever user disconnects sync. This might be the simpler 80% solution to go with for now.

Comment 1

[Firefox Bug Husbandry Bot]

Re-triaging per https://bugzilla.mozilla.org/show_bug.cgi?id=1473195

Needinfo :susheel if you think this bug should be re-triaged.

Comment 2

[BMO Automation]

We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.