Hi,
We’re seeing a small, but meaningful number of events being rejected due to:
{
"schemaKey": "iglu:com.snowplowanalytics.snowplow/browser_context/jsonschema/1-0-0",
"error": {
"error": "ValidationError",
"dataReports": [
{
"message": "$.deviceMemory: number found, but [integer, null] is required",
"path": "$.deviceMemory",
"keyword": "unionType",
"targets": [
"number",
"[integer, null]"
]
}
]
}
}
Some values we get for deviceMemory are: 0.5, “16”
- These events seem valid (not malicious or spam) so, since browser_context comes from the JS tracker, so why does it produce illegal values?
- And/or should the iglu schema for browser_context should be updated and relaxed to allow numbers and strings?
- Anything we can do more immediately to workaround this issue?