Horizon OS Store Setup

Required Values#

Horizon setup has one OpenIAP-specific configuration value. It is the Meta app id for the Horizon app record, not the Android package name.

Store Prerequisites#

Complete these once per app in Meta Horizon Developer Hub before configuring any framework:

1. Register the app in Meta Horizon Developer Hub.
2. Create your products and subscriptions with stable SKUs — the same strings you will pass to fetchProducts and requestPurchase.
3. Copy the Horizon app id so the Android manifest can read it at build time.
4. Prepare a Meta Quest device signed into an account that has access to the app, such as a release-channel member or registered test user.

Framework Setup#

Every framework except Godot ships Quest support through the same Android horizon flavor; only the switch location differs. Find your framework here, then follow the matching section below for full snippets.

Native Android#

Use the Horizon artifact directly, or select the local Gradle flavor when building from source:

dependencies {
    implementation("io.github.hyochan.openiap:openiap-google-horizon:3.5.0")
}

android {
    defaultConfig {
        missingDimensionStrategy("platform", "horizon")
    }
}

Provide the app id in the Android manifest:

<meta-data
    android:name="com.meta.horizon.platform.HORIZON_APP_ID"
    android:value="YOUR_HORIZON_APP_ID" />

Expo#

Expo apps should let the expo-iap config plugin write the Gradle flavor, dependency, and manifest app id during prebuild:

plugins: [
  [
    'expo-iap',
    {
      modules: {
        horizon: true,
      },
      android: {
        horizon: {
          appId: 'YOUR_HORIZON_APP_ID',
        },
      },
    },
  ],
]

React Native#

react-native-iap has no Expo config plugin, so select the Horizon flavor in the app Gradle build and write the app id in the manifest yourself. fireOsEnabled is the switch for Amazon Fire OS builds; the two flavors are mutually exclusive, so keep it false for Quest artifacts:

# android/gradle.properties
horizonEnabled=true
fireOsEnabled=false
horizonAppId=YOUR_HORIZON_APP_ID

// android/app/build.gradle
android {
    defaultConfig {
        def horizonEnabled = project.findProperty('horizonEnabled')?.toBoolean() ?: false
        def fireOsEnabled = project.findProperty('fireOsEnabled')?.toBoolean() ?: false
        if (horizonEnabled && fireOsEnabled) {
            throw new GradleException("horizonEnabled and fireOsEnabled cannot both be true")
        }
        def flavor = fireOsEnabled ? 'amazon' : (horizonEnabled ? 'horizon' : 'play')
        missingDimensionStrategy "platform", flavor

        manifestPlaceholders = [
            HORIZON_APP_ID: project.findProperty('horizonAppId') ?: ''
        ]
    }
}

<meta-data
    android:name="com.meta.horizon.platform.HORIZON_APP_ID"
    android:value="${HORIZON_APP_ID}" />

Flutter#

Flutter uses the same Gradle property model as bare React Native. The app module maps the property into the plugin flavor and injects the app id through a manifest placeholder; localProperties is the loader the Flutter Android template already defines in android/app/build.gradle:

# android/gradle.properties
horizonEnabled=true
fireOsEnabled=false

# android/local.properties
HORIZON_APP_ID=YOUR_HORIZON_APP_ID

def horizonEnabled = project.findProperty('horizonEnabled')?.toBoolean() ?: false
def fireOsEnabled = project.findProperty('fireOsEnabled')?.toBoolean() ?: false
def flavor = fireOsEnabled ? 'amazon' : (horizonEnabled ? 'horizon' : 'play')

android {
    defaultConfig {
        missingDimensionStrategy 'platform', flavor
        manifestPlaceholders = [
            HORIZON_APP_ID: localProperties.getProperty("HORIZON_APP_ID") ?: ""
        ]
    }
}

Reference the placeholder in the Android manifest:

<meta-data
    android:name="com.meta.horizon.platform.HORIZON_APP_ID"
    android:value="${HORIZON_APP_ID}" />

KMP and MAUI#

KMP publishes per-store Android variants of the library; Quest apps consume the horizonRelease variant and keep the app id in the Android host app's manifest, exactly as in the Native Android section above. When building the library from source, assemble the variant directly:

./gradlew :library:assembleHorizonRelease

MAUI selects the Horizon AAR flavor with an MSBuild property:

dotnet build -f net10.0-android -p:OpenIapAndroidStore=horizon

Verification#

Client purchase calls stay the same on Quest — fetchProducts and requestPurchase work unchanged. For server validation, pass the Horizon receipt context to Validation or to IAPKit, OpenIAP's hosted verification backend, using the horizon payload:

await verifyPurchase({
  horizon: {
    sku: purchase.productId,
    userId: metaUserId,
    accessToken: horizonAccessToken, // Meta app credential
  },
});

The access token is a Meta app credential. Keep Horizon verification on trusted infrastructure — your backend or IAPKit — rather than embedding the token in the shipped app.