Meta Quest Upload Rejected? Fix Orientation, Signing and Manifest Errors in Unreal Engine

Table of Contents

Unreal Engine 5.8, Meta Quest 3. Updated November 2026. Written by the Algosyntax team.

Quick answer: Unreal’s default Android settings don’t match what Meta’s Developer Dashboard accepts. Before you upload:

  • Set Orientation to Landscape. Unreal writes sensorLandscape by default, and Meta rejects it.
  • Sign the APK with your own release keystore, and package for distribution.
  • Remove what Quest doesn’t use: Google Play billing and AdMob.
  • Decide between one APK and an APK plus OBB.
  • Raise the version code for every upload.

All the settings below are in Config/DefaultEngine.ini under [/Script/AndroidRuntimeSettings.AndroidRuntimeSettings] unless noted. Most also appear in Project Settings > Platforms > Android. We found these while submitting VR Musician.

“APK screen orientation is not landscape”

This was the upload error we actually got:

APK screen orientation is not landscape (android:screenOrientation in AndroidManifest.xml)

Unreal’s default orientation writes android:screenOrientation="sensorLandscape" into the manifest. Meta wants plain landscape. Set:

Orientation=Landscape

Package again. Our next upload with this one change was accepted.

Sign with your own release key

Meta rejects APKs signed with the Android debug key. Create a keystore once with keytool, which comes with the JDK. Run it in your project’s Build/Android folder and type the passwords when asked:

keytool -genkeypair -v -keystore MyGame-release.keystore -alias mygame -keyalg RSA -keysize 2048 -validity 10000

Then in Project Settings > Platforms > Android > Distribution Signing, set Key Store to the file name only, plus Key Alias and Key Store Password. Leave Key Password empty if it’s the same.

Turn on For Distribution in Project Settings > Packaging (stored as ForDistribution=True in DefaultGame.ini). That also makes the APK non-debuggable, which Meta requires. Packaging fails until signing is set, which is a useful check.

Check the result with apksigner verify --verbose YourGame.apk from the Android build-tools. Meta requires v2 signing, and the output should say it’s verified with v2.

Two warnings. Back up the keystore and its password outside the project. If you lose them, you can’t publish updates to the same store listing. And Unreal saves the keystore passwords in plain text in DefaultEngine.ini, so don’t commit those lines to a shared or public repository. If they were ever pushed, treat the password as exposed.

Manifest settings for Meta’s store requirements

Requirement Unreal default Setting
Install location auto internalOnly InstallLocation=Auto
Hidden from the recent apps list Missing +ExtraActivityNodeTags=android:excludeFromRecents="true"
No unused permissions or Google services Adds com.android.vending.BILLING and an AdMob activity bSupportAdMob=False, and in [OnlineSubsystemGooglePlay.Store]: bSupportsInAppPurchasing=False
Supported headsets and hand tracking None ExtraApplicationSettings with com.oculus.supportedDevices and com.oculus.handtracking.frequency (example below)
A new version code per upload 1 Raise StoreVersion every time

Our hand-tracking settings:

+ExtraPermissions=com.oculus.permission.HAND_TRACKING
ExtraApplicationSettings=<meta-data android:name="com.oculus.supportedDevices" android:value="quest2|questpro|quest3|quest3s" />\n<meta-data android:name="com.oculus.handtracking.frequency" android:value="HIGH" />

Array settings such as ExtraPermissions and ExtraActivityNodeTags need the + in front, or they replace the engine’s list instead of adding to it.

We set these from Meta’s packaging checklist before uploading. Only the orientation came back as an actual rejection.

One APK, or APK plus OBB?

By default Unreal puts the game data in a separate OBB file. Ours was a 78 MB APK plus a 530 MB OBB, and the app won’t run without the OBB. To ship one file instead:

bPackageDataInsideApk=True

That gave one APK of about 580 to 610 MB. One file is simpler to upload and to install for testers. Keep it under the size limit of the store or competition you’re submitting to; above that, switch back to an OBB.

If packaging fails after the APK is built

Our first data-in-APK build failed at the very end: the Android File Server plugin tried to build its helper APK after the real APK was done, so the archive step never ran and the APK stayed in Binaries/Android. Turn the plugin off for release builds:

[/Script/AndroidFileServerEditor.AndroidFileServerRuntimeSettings]
bEnablePlugin=False

The output folder also contains an AFS_....apk helper. Don’t upload that one.

Uploading in the Developer Dashboard

  • Devices: only tick headsets you have actually tested on. Review checks performance on every device you tick. We ticked only the Quest 3 family.
  • Extra files: if the data is inside the APK, skip the OBB, asset files and debug symbols.

Keep build output out of Git

A 608 MB APK in a commit gets your push rejected with GH001: Large files detected on GitHub, whose limit is 100 MB per file. Add your packaging folder (for example Packaged/), Saved/, Binaries/ and *.keystore to .gitignore before your first package.

FAQ

Does Unreal have a single “Meta Quest store” checkbox? Package for Meta Quest devices sets up the headset-specific parts of the manifest, but not the items above. You still set those yourself.

Do I need the Meta XR plugin? Not for packaging. Everything here works with Unreal’s built-in OpenXR plugins.

Related tutorials