Missing known device/GPU details (processor, unique ID, support for ...)

[ShawnCZek]

Environment

self-hosted (https://develop.sentry.dev/self-hosted/)

Version

22.12.0

Link

No response

DSN

No response

Steps to Reproduce

1. Create a new exception event
2. Add a device context and include one or more of the following keys:
   • device_unique_identifier
   • processor_count
   • processor_frequency
   • supports_accelerometer
   • supports_audio
   • supports_gyroscope
   • supports_location_service
   • supports_vibration
3. Add a GPU context and include one or more of the following keys:
   • max_texture_size
   • graphics_shader_level
   • supports_draw_call_instancing
   • supports_ray_tracing
   • supports_compute_shaders
   • supports_geometry_shaders
4. Send the event to a native project
5. View the event in issues

Expected Result

Values of the mentioned keys will be appropriately formatted or at least visible as they are described in the documentation: https://develop.sentry.dev/sdk/event-payloads/contexts/#device-context

Actual Result

Right now, the values for the device context are not even displayed in the administration, supposedly due to how unknown keys are handled:

sentry/static/app/components/events/contexts/device/getDeviceKnownDataDetails.tsx

Lines 222 to 223 in 664e9c8

	default:
	return undefined;

This is what it looks like in the administration:

And this is the JSON of the device context from the event:

On the other hand, the mentioned keys of the GPU context are shown in the administration. They are just not properly formatted:

[getsantry]

Assigning to @getsentry/support for routing, due by Tue Jan 10 2023 18:26:05 GMT+0000. ⏲️

[getsantry]

Routing to @getsentry/open-source for triage, due by Wed Jan 11 2023 19:04:15 GMT+0000. ⏲️

[hubertdeng123]

Seems like this is something that the native team might have more context on, rerouting there!

[getsantry]

Routing to @getsentry/owners-native for triage, due by Fri Jan 13 2023 18:09:55 GMT+0000. ⏲️

[Swatinem]

The added props seem to be there in the JSON (or at least half the supports_X props), so this is rather something for UI.

[getsantry]

Routing to @getsentry/core-ui for triage, due by Sat Jan 14 2023 01:00:00 GMT+0000. ⏲️

[evanpurkhiser]

@priscilawebdev do you know why this returns undefined here

sentry/static/app/components/events/contexts/device/getDeviceKnownDataDetails.tsx

Lines 222 to 223 in 664e9c8

	default:
	return undefined;