An open-source Ray-Ban Meta glasses app kept eight API keys in plain text until October 4

An open-source Ray-Ban Meta glasses app kept eight API keys in plain text until October 4

An open-source iPhone app that puts a choice of AI models on Ray-Ban Meta glasses kept eight API keys and tokens unencrypted in its own settings file, and the change that moves them into the iOS Keychain merged on October 4 at 19:19 UTC. The app is OpenVision, a third-party project published under the MIT licence, and none of it is Meta's.

A library illustration of glowing letters falling towards a circular mirror. The eight credentials move out of a file in the app's Documents directory and into the iPhone's Keychain.

The work arrived as a pull request titled "Add: Store API keys in the Keychain", opened on October 3 at 07:56 UTC by the contributor raphaelbarreiros and merged a day and a half later across eight files. It says the eight keys and tokens "were saved in plain text in Documents/settings.json" and now go to the Keychain as items readable after the phone's first unlock.

The pull request names them: openClawAuthToken, geminiAPIKey, openAIAPIKey, grokAPIKey, hermesAPIKey, tavilyAPIKey, telemetryToken and telemetryPassword. Anyone running OpenVision against OpenAI, Google's Gemini, xAI's Grok or the search service Tavily supplied those credentials themselves, because the app runs on the owner's own accounts.

OpenVision's own summary counts five backends and its README counts seven, among them on-device MLX models, Apple Intelligence, Gemini Live and OpenClaw. The glasses provide the camera and the microphone; the model runs on the phone or in a cloud account the owner pays for, and pairing still goes through Meta's own companion app, which the company makes a requirement for managing its glasses.

The keys still travel with an iPhone backup

The new Keychain items are not marked this-device-only, unlike the app's sign-in tokens, so by the project's own account "the keys still move with an encrypted backup or Quick Start to a new phone, as they did in settings.json". What changes is that the settings file is written with those fields blank.

Migration runs on launch. A settings file from an older build still holds the keys, so they are read from it, saved straight away, and blanked where they were; a secret whose Keychain write fails stays in the file.

Before the change the file sat in the app's own sandboxed Documents directory, which other iPhone apps cannot read, and it was carried into an encrypted iPhone backup. The project has published no security advisory, and there is no CVE.

One contributor ran 131 tests on one phone

Testing was done on an iPhone 16 Pro Max running iOS 27.2, and the project reports that "the full suite passed on the device: 131 tests, 0 failures". The contributor also notes that his own phone had no API keys set, so the migration path ran there only through unit tests.

Clearing a key in the app's settings now deletes its Keychain item, and "Reset to defaults" clears all of them. Installing an older build after this one shows blank keys, because the file no longer carries them, and anyone who hand-edited that file to move credentials between phones will find it empty.

Most readers cannot install this at all

There is no App Store listing. The documented route is a source build in Xcode on a Mac, which puts OpenVision in the same bracket as the third-party wrappers built on Meta's glasses toolkit, which Meta will not let developers publish.

The repository showed 153 stars and 35 forks when it was read at 00:01 UTC on October 5, against a first commit in February, and its last push came at 20:48 UTC on October 4. The change closes an issue raised as a follow-up to an earlier review of the same code.

Leave a Comment

Your email address will not be published. Required fields are marked *