Closed Bug 1787928 Opened 3 years ago Closed 3 years ago

In Fenix 103.1.0 and later `client_info.os_version` is nearly always "Unknown"

Categories

(Data Platform and Tools :: Glean: SDK, defect, P1)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: srose, Assigned: janerik)

References

Details

(Whiteboard: [dataquality])

Attachments

(1 file)

And when client_info.os_version is "Unknown" normalized_os_version ends up being an empty string.

This seems like it might be related to the cause of bug 1781085 "Fenix release seeing an increase in null values in client_info fields".

I say "nearly always" because there are a very small number of clients (e.g. 0.002%) that are recording proper client_info.os_version values.

Blocks: 1774051

glean-core ignores the passed-in value of ClientInfoMetrics::os_version and uses the value it can detect itself.

For whatever reason, this doesn't get the value of Build.VERSION.RELEASE provided by the embedder in Kotlin.

If this is an intentional (but partial) deprecation of the os_version field in ClientInfoMetrics we'll need some release notes, a Notable Historical entry, and some additional mailing list comms. If this is accidental, I think all we need to do is use any provided os_version, only defaulting to system::get_os_version() on None.

Assignee: nobody → jrediger
Depends on: 1788040
Priority: -- → P1

The release landed in Fenix.
https://sql.telemetry.mozilla.org/queries/87721/source#217360 shows that the latest builds report a known os version again.

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Whiteboard: [data-quality] → [dataquality]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: