Closed
Bug 1523939
Opened 6 years ago
Closed 5 years ago
Investigation: does glean really need an `initialize` method on Android?
Categories
(Data Platform and Tools :: Glean: SDK, enhancement, P3)
Data Platform and Tools
Glean: SDK
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: Dexter, Unassigned)
References
Details
(Whiteboard: [telemetry:glean-rs:backlog])
Apparently, on Android, there's a way to automatically init things by using ContentProviders
. This is not official, however Google does it quite in a few places so it should be safe enough (thanks Sebastian for finding this!).
The WorkManager
library for scheduling background jobs, has an interesting comment in the initialize()
method. And the docs say: "By default, this method should not be called because WorkManager is automatically initialized."
They do that by defining a ContentProvider
:
The ContentProvider
will do the initialization:
After creating the application process Android will create an instance of all ContentProviders
(that is not really documented)
Reporter | ||
Updated•6 years ago
|
Priority: -- → P3
Updated•6 years ago
|
Whiteboard: [telemetry:mobilesdk:m?] → [telemetry:mobilesdk:backlog]
Reporter | ||
Updated•5 years ago
|
status-firefox67:
affected → ---
Component: Telemetry → Glean: SDK
Product: Toolkit → Data Platform and Tools
Version: Trunk → unspecified
Updated•5 years ago
|
Whiteboard: [telemetry:mobilesdk:backlog] → [telemetry:glean-rs:m?]
Reporter | ||
Updated•5 years ago
|
Summary: Investigation: does glean really need an `initialize` method? → Investigation: does glean really need an `initialize` method on Android?
Whiteboard: [telemetry:glean-rs:m?] → [telemetry:glean-rs:backlog]
Updated•5 years ago
|
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•