You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 20, 2023. It is now read-only.
Note: the app_opened_all_startup captures app startup (i.e. app background to foreground) and includes if the link came from app_link. As a solution to this issue, assuming I understand the probe correctly, we could merge the NORMAL/PRIVATE state to the app_opened_all_startup probe to get the same results.
If you correct the existing probe, don't forget to:
mcomella
changed the title
[Bug] opened_link telemetry is wrong: reports twice when it should report once
[Bug] opened_link telemetry is wrong: reports twice when it should report once on cold app link
Aug 24, 2020
mcomella
added a commit
to mcomella/fenix
that referenced
this issue
Aug 24, 2020
See: #17373 This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
See: #17373 This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Steps to reproduce
adb shell am start -n org.mozilla.fenix.debug/mozilla.telemetry.glean.debug.GleanDebugActivity --es tagPings correctness --es sendPing events
)Expected behavior
opened_link
appears onceActual behavior
opened_link
appears twiceDevice information
Note: the
app_opened_all_startup
captures app startup (i.e. app background to foreground) and includes if the link came fromapp_link
. As a solution to this issue, assuming I understand the probe correctly, we could merge theNORMAL
/PRIVATE
state to theapp_opened_all_startup
probe to get the same results.If you correct the existing probe, don't forget to:
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: