Closed
Bug 1111707
Opened 11 years ago
Closed 10 years ago
Telemetry clientID always "null" on Fennec
Categories
(Toolkit :: Telemetry, defect)
Toolkit
Telemetry
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: vladan, Unassigned)
References
(Blocks 1 open bug)
Details
Whenever I check the about:telemetry page in release Fennec 34 on my HTC One M8, I see that the clientID field is null, regardless of the browser uptime
Comment 1•11 years ago
|
||
This is to be expected because FHR on Android is done in Java not gecko.
Comment 2•11 years ago
|
||
I dont think clientID is important for Fennec telemetry right now (from what i know FHR is still the major focus on mobile anyway).
We can revisit this if the mobile team requires it (or when we do the unification on mobile too).
Updated•11 years ago
|
OS: Windows 7 → All
Hardware: x86_64 → All
Version: 34 Branch → Trunk
Updated•11 years ago
|
Updated•10 years ago
|
Comment 3•10 years ago
|
||
rvitillo found that we are submitting client ids on Fennec now (probably as a result of making the client id implementation independent of the desktop FHR code).
mfinkle and i don't see any code in mobile FHR that adds a client id - it looks like Fennec FHR never submitted a client id?
Flags: needinfo?(rnewman)
Comment 4•10 years ago
|
||
The v3 FHR document format has no clientID (neither did v2 at the time, IIRC), so Fennec's FHR doesn't include one.
Flags: needinfo?(rnewman)
Comment 5•10 years ago
|
||
That is bug 981698.
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
Comment 6•10 years ago
|
||
Georg, I'm confused about the resolution of this. Presumably we will need a clientID on Android, and bug 981698 is about FHRv3 which is going away.
Flags: needinfo?(gfritzsche)
Comment 7•10 years ago
|
||
This is already working since we moved the client id implementation out of the desktop FHR code (bug 1137353 et al).
Flags: needinfo?(gfritzsche)
You need to log in
before you can comment on or make changes to this bug.
Description
•