Open
Bug 1947173
Opened 1 month ago
Updated 8 days ago
GleanDebugActivity doesn't produce logs before onboarding flow
Categories
(Data Platform and Tools :: Glean: SDK, defect, P4)
Data Platform and Tools
Glean: SDK
Tracking
(Not tracked)
NEW
People
(Reporter: polly, Unassigned)
Details
When debugging glean pings in Fenix using a command such as:
adb shell am start -n org.mozilla.fenix.debug/mozilla.telemetry.glean.debug.GleanDebugActivity \
--ez logPings true
Nothing appears in logcat
until after the onboarding flow is complete.
We think this is because the glean log level command is passed in during init, which is now delayed until after onboarding.
Comment 1•1 month ago
|
||
For context:
In bug 1900308 we moved log init to Glean.init to avoid calling into glean-core early.
That's why now we don't get those logs until Glean is initialized and due to the onobardinf flow that initalization might be delayed.
While we can maybe re-enable the logs (by doing just the log init early once we have libxul loaded, but not Glean init), triggering pings through the debug activity will still not actually submit anything until after onboarding of course.
Updated•1 month ago
|
Priority: -- → P3
Updated•8 days ago
|
Priority: P3 → P4
You need to log in
before you can comment on or make changes to this bug.
Description
•