Mapping Apple Device Identifiers to Friendly Names

I find it annoying when a UI shows iPad16,6 instead of a name I actually recognize. It makes debugging harder and the interface feels unfinished. I use a local database to map these identifiers to friendly names so I can tell exactly which device is which in the Instances UI.

What You’ll Need

• Access to the kyle-seongwoo-jun/apple-device-identifiers repository.
• The local directory apps/macos/Sources/OpenClaw/Resources/DeviceModels/.

Quick Start

I keep the mapping as pinned JSON files to ensure builds stay deterministic. To update the database, follow these four steps:

1. Pick the upstream commits you want to pin for iOS and macOS.
2. Update those commit hashes in apps/macos/Sources/OpenClaw/Resources/DeviceModels/NOTICE.md.
3. Run these commands to download the latest pinned files:

IOS_COMMIT="<commit sha for ios-device-identifiers.json>"
MAC_COMMIT="<commit sha for mac-device-identifiers.json>"

curl -fsSL "https://raw.githubusercontent.com/kyle-seongwoo-jun/apple-device-identifiers/${IOS_COMMIT}/ios-device-identifiers.json" \
  -o apps/macos/Sources/OpenClaw/Resources/DeviceModels/ios-device-identifiers.json

curl -fsSL "https://raw.githubusercontent.com/kyle-seongwoo-jun/apple-device-identifiers/${MAC_COMMIT}/mac-device-identifiers.json" \
  -o apps/macos/Sources/OpenClaw/Resources/DeviceModels/mac-device-identifiers.json

4. Check apps/macos/Sources/OpenClaw/Resources/DeviceModels/LICENSE.apple-device-identifiers.txt against the upstream license and replace it if the upstream version changed.

Troubleshooting

If you want to ensure the JSON update didn’t break the application, you should check for build warnings. I use this command to verify that everything is correctly linked:

swift build --package-path apps/macos

结尾

Need help with the setup? Talk to the AI Setup Assistant.

What’s Next

• Instances UI Overview
• Managing macOS Resources