From meta-vr
Upgrades Meta Quest apps to newer Horizon OS SDK versions with migration guides, deprecated API replacements, and changelog references.
How this skill is triggered — by the user, by Claude, or both
Slash command
/meta-vr:hz-api-upgradeThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill when:
Use this skill when:
Every SDK upgrade, regardless of platform, follows the same high-level process:
Determine what version the project currently targets:
Packages/manifest.json or the Package Manager UI for com.meta.xr.* package versions.uplugin files or the Plugins browserbuild.gradle or build.gradle.kts for com.meta.spatial:* dependency versionspackage.json for @meta-spatial-sdk/* or @iwsdk/* package versionsBefore upgrading, review what changed between your current version and the target version. See references/api-changelog.md for a summary of recent changes.
Use the device hub to search documentation:
metavr docs search "release notes v72"
metavr docs search "migration guide openxr"
Update the version numbers in your project configuration:
manifest.json directlybuild.gradlenpm update or edit package.jsonAfter updating, compile the project and address errors and warnings. See references/deprecation-guide.md for common replacements.
# Search project for known deprecated APIs
grep -rn "vrapi_" --include="*.c" --include="*.cpp" --include="*.h" src/
grep -rn "OVRManager" --include="*.cs" Assets/
Deploy and verify functionality on a connected Quest device:
metavr app install ./build/output.apk
metavr app launch com.yourcompany.yourapp
Ensure the upgrade did not introduce performance regressions:
metavr perf capture
The Meta XR SDK for Unity is distributed as UPM packages. Upgrades are performed through the Unity Package Manager. Key packages include com.meta.xr.sdk.core, com.meta.xr.sdk.interaction, and com.meta.xr.sdk.platform.
See references/sdk-migration.md for the step-by-step Unity upgrade guide.
The Meta XR Plugin for Unreal is distributed as an engine plugin. Upgrades involve downloading the new plugin version and regenerating project files.
See references/sdk-migration.md for the step-by-step Unreal upgrade guide.
The Meta Spatial SDK is distributed as Gradle dependencies. Upgrades involve bumping version numbers in your Gradle build files.
See references/sdk-migration.md for the step-by-step Spatial SDK upgrade guide.
The Immersive Web SDK is distributed as npm packages. Upgrades involve updating package versions in package.json.
See references/sdk-migration.md for the step-by-step IWSDK upgrade guide.
Meta has progressively moved from Oculus.* and OVR* namespaces to Meta.* namespaces. After an upgrade, you may see compilation errors due to renamed classes or moved packages.
APIs that were deprecated in previous versions may be fully removed in newer versions. If you skipped intermediate upgrades, you may encounter missing symbols. Always upgrade incrementally.
Newer Horizon OS versions may require additional permissions in your AndroidManifest.xml. Common additions include:
com.oculus.permission.HAND_TRACKING for hand tracking featureshorizonos.permission.HEADSET_CAMERA for passthrough camera access<meta-data> entries for feature declarationsNewer SDK versions may require updated <meta-data> entries in AndroidManifest.xml, such as com.oculus.supportedDevices or updated minSdkVersion values.
New binary uploads for Meta Horizon apps must set targetSdkVersion within the supported range.
targetSdkVersion to API level 32-34 for immersive apps (or 32-36 for 2D panel apps)minSdkVersion can remain at API level 32Unity: Use the Project Setup Tool in the Meta XR SDK -- it can update API versions automatically. Or manually set in Player Settings -> Other Settings -> Target API Level.
Unreal: Use the Project Setup Tool in the Meta XR Plugin. Or set in Project Settings -> Android -> Target SDK Version.
Gradle (Spatial SDK / Native):
android {
defaultConfig {
targetSdkVersion 34 // 32-34 for immersive, 32-36 for 2D panel apps
minSdkVersion 32
}
}
The metavr tool provides documentation search to help during upgrades. Invoke via metavr <args> (published as the npm package metavr; if metavr is not on PATH, run npx -y metavr <args>) — no global install needed.
# Search for migration-related documentation
metavr docs search "migration guide"
metavr docs search "deprecated API"
metavr docs search "breaking changes v73"
# Search for specific API replacements
metavr docs search "OVRManager replacement"
metavr docs search "vrapi openxr migration"
npx claudepluginhub meta-quest/agentic-tools --plugin meta-vrPre-flight check that verifies Meta Quest VR code and answers against official Meta documentation via metavr CLI, preventing stale or deprecated APIs.
Upgrades Expo SDK versions with guidance on breaking changes, dependency updates, and configuration migration.
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.