Confirm an official glasses app build before you install

Time needed about 45 minutes, spread over two sessions

The steps

1. Find the store listingOpen the App Store, Google Play, or your headset vendor’s app store and search for the app name you were givenYou should see: You see a store page that shows the app, the publisher name, and a link to more information or support
2. Confirm the publisher identityCompare the publisher name on the store page to the company claiming authorship of the buildYou should see: The publisher listed in the store matches the company that claims to publish the build
3. Check release notes for device modelOpen the release notes or changelog on the store page or vendor support article and search for your headset model nameYou should see: Release notes explicitly list your headset model or family as supported
4. Verify vendor support linksLook for a vendor support article or knowledgebase entry that links to the same store page or build you were givenYou should see: A vendor support page links to the app listing or to a download URL owned by the vendor
5. Get the package name and signing fingerprintIf the build is sideloaded, ask the publisher for the exact package name and the signing certificate fingerprint (full string)You should see: You receive a package name and a fingerprint you can compare character-for-character
6. Match fingerprints and package namesUse a trusted tool or ask the vendor to confirm the fingerprint of the binary you were given matches their published fingerprintYou should see: The package name and fingerprint match the vendor’s published values exactly
7. Limit permissions and create a recoveryBefore installing an unofficial build, create a device backup or restore point and restrict app permissions (camera, mic, storage)You should see: A backup exists and permission prompts are limited during the app’s first run
8. Ask the vendor for confirmationIf any check fails or remains unclear, contact vendor support with the package name and fingerprint and request written confirmationYou should see: Vendor support confirms whether they produced and signed the build, or they decline

How to tell if a glasses app is an official build

An app is official when the device maker or the app publisher publishes and signs a build for your exact headset and links it from their store or support pages. To confirm, check the store listing, the publisher identity, release notes that name your model, and the package signature or vendor-provided download link.

What clear signals show a build is official

Four concrete signals prove an official build: a vendor store or App Store listing for your model, the publisher account matching the app owner, release notes that name the headset model, and a vendor support article or download link. When these four match, you have end-to-end provenance from marketing to engineering.

• Vendor or App Store listing visible to consumers
• Publisher account identity matches the app owner
• Release notes explicitly mention your headset model
• Vendor support article or knowledgebase linking to the build

How to verify signed binaries on Apple Vision Pro

For Apple Vision Pro the App Store listing and the developer identity shown there are the only reliable signals. An app available in the Vision Pro App Store under the publisher’s developer account counts as official for that headset. Do not install Vision Pro binaries offered outside the App Store; unsigned consumer installs are unsupported.

How to verify signed packages and provenance on Android XR and sideloads

Android XR headsets use APK/AAB packages. Official installs come from Google Play, the device maker’s store, or a vendor-provided signed package. Verify three items: the package name, the exact signing certificate fingerprint, and the vendor link that published the build. Any mismatch means the binary is not the vendor’s official build.

• If the app is on Google Play, use that listing and publisher name first
• For sideloads, get the package name and the signing fingerprint from the publisher
• Different fingerprints indicate a rebuild or repackaging

Vendor stores and device-specific checks: Ray‑Ban Meta and XREAL

Ray‑Ban Meta and XREAL publish device pages or vendor stores that list supported apps. An app listed on a device page that names your model is authoritative. Cross-check the vendor listing, the publisher name, and any support article or linked APK to confirm the same package name and fingerprint before you install.

• Use vendor device pages, not third-party app collections, to confirm model support
• Compare vendor links against our Ray‑Ban Meta page /devices/ray-ban-meta and XREAL page /devices/xreal-air-2-ultra
• If a vendor support page links directly to a download, note the URL and publisher identity

Step-by-step checklist you must run before installing any unknown build

Run these checks in order. Each step removes a class of fake builds. After each check you should have a concrete artifact to compare: a store URL, a publisher name, release notes, a vendor support article, or a signing fingerprint.

• Confirm whether the app is listed on Apple App Store, Google Play, or the vendor’s store
• Confirm the publisher identity on the listing matches the company claiming authorship
• Find release notes that name your exact headset model or family
• If sideloading, obtain and match the package name and signing fingerprint to the publisher’s published fingerprint
• Confirm a vendor support article links to the build or documents support for it
• If only community builds exist, get vendor permission or prefer not to install

When a community port is the only option — how to proceed safely

Community ports are unofficial. Ask the app publisher to confirm authorship, provide the package name and signing fingerprint, or publish an official build. If the publisher cannot confirm, accept the support risk: limit permissions, keep backups, and prepare a recovery plan before you install.

• Ask the publisher for explicit confirmation and a fingerprint before you install
• Limit app permissions and remove camera/microphone access where possible
• Keep a recovery plan: a backup of headset settings or a known good image

How this verification process fails in real projects and what to watch for

Most failures begin with trusting one signal: a GitHub release or forum post without vendor confirmation. Users install a binary because basic flows work, then face crashes or security issues with no vendor support. Also watch for signature mismatches where the APK is signed by a different certificate than the store listing.

• Single-signal trust: relying on a GitHub binary without a vendor link
• Signature mismatch: package name looks right but signing certificate differs
• No support route: no vendor support article or contact to escalate a problem

What to do next

Compare the build you were offered against our directory at /apps and the vendor device page for your headset. Use those pages to confirm store listings and vendor support links. If anything is unclear, ask vendor support for the exact package name and the signing fingerprint and match both before you install.

Where this usually goes wrong

• The app runs but crashes on specific featuresThe build was not tested on your headset model and lacks device-specific fixesReinstall only a vendor-provided build or ask the vendor for a patched build; restore your backup if needed
• Publisher name on the store differs from the one who provided the binaryThe binary was repackaged by a third party or the publisher uses a different accountDo not install; request a build directly from the publisher and verify fingerprints
• No vendor support article or contact exists for the buildThe build was distributed informally without vendor endorsementTreat as unofficial, keep the build off production devices, and ask the app owner to publish an official build
• Signing fingerprint does not match vendor-published fingerprintThe binary has been rebuilt or tampered withDo not install; obtain the official build or use only store-distributed versions

The checklist

• Find the store listing
• Confirm the publisher identity
• Check release notes for device model
• Verify vendor support links
• Get the package name and signing fingerprint
• Match fingerprints and package names
• Limit permissions and create a recovery
• Ask the vendor for confirmation

Frequently asked questions