Closed
Bug 1933176
Opened 3 months ago
Closed 3 months ago
[Experiment] The “Tab swipe” CFR message does not generate any telemetry
Categories
(Fenix :: Experimentation and Telemetry, defect)
Tracking
(firefox134 affected)
RESOLVED
DUPLICATE
of bug 1932553
Tracking | Status | |
---|---|---|
firefox134 | --- | affected |
People
(Reporter: vbandac, Unassigned)
References
(Blocks 1 open bug)
Details
[Affected versions]:
- Firefox Nightly 134.0a1 (BUILD ID #2016058114), hg-c0c4c089fc10+, GV: 134.0a1-20241124222624, AS: 134.20241122050253
[Affected Platforms]:
- Samsung A53 - Android 14
- OnePlus 6 - Android 11
[Prerequisites]:
- Have the latest Firefox Nightly 134.0a1 installed, but not opened.
- Have the latest version of nimbus-cli installed.
- Have the mobile device connected to a computer using adb.
[Steps to reproduce]:
- Run the following command in a terminal:
nimbus-cli --app fenix --channel nightly enroll preview/combined-android-toolbar-and-menu-experiment --branch treatment-a
. - Close the browser and open it using a telemetry command (
adb shell am start -n org.mozilla.fenix/mozilla.telemetry.glean.debug.GleanDebugActivity --ez logPings true --es sendPing events --es debugViewTag <chosen_tag>
).
3.Open at least two tabs. - From a loaded webpage, go to the tabs tray and navigate to the next or previous tab.
- Dismiss the “Tab swipe” CFR message by tapping the “X” button.
- Navigate to the Glean viewer and observe the events displayed.
[Expected result]:
- A CFR related ping should be registered in Glean for the message being displayed and dismissed.
[Actual result]:
- No CFR related ping is recorded for these actions.
[Notes]:
- This issue is reproducible on both Treatment branches of the experiment.
Comment 1•3 months ago
|
||
Thanks. This missing telemetry will be added in bug 1932553.
You need to log in
before you can comment on or make changes to this bug.
Description
•