Realm Studio fails to parse UUIDs of versions 1-3 and 5-8, showing error in column instead #1681
Description
Describe the bug
Realm Studio 20.0.0 fails to parse and display UUIDs of versions 1–3 and 5–8, even though Realm itself supports them. Only v4 UUIDs display correctly. Other versions trigger the following error:
UUID string representations must be a 32 or 36 character hex string (dashes excluded/included). Format: "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" or "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx".
To Reproduce
- Download and extract RealmGuidExample.zip
- Open the .NET 9.0 solution 'RealmGenerator' and run in debug mode
- Inspect Realm database instance in 'RealmDB' folder using Realm Studio 20.0.0
- Observe parsing errors in the ID column
Expected behavior
Realm Studio should support viewing and editing all valid UUIDs, regardless of version.
Versions:
- OS: MacOS Sequoia 15.5
- Realm Studio Version: 20.0.0
- Realm Nuget version: 20.1.0
Screenshots
Additional context
Realm itself handles all UUID versions correctly at runtime (verified via .NET). However, Realm Studio fails to display them, which prevents us from migrating legacy data generated with v1 UUIDs. Those values are currently stored as strings, and migration to the UUID type is blocked by this issue.