# Meta Quest 3

These screenshots show the Unity 6 and device settings required to successfully deploy and launch apps on the Meta Quest 3.

## Settings & Permissions in Unity

#### 1. Build Profiles > Android > MetaQuest Profile > Scene List & Scripting Defines

Ensure that you have a Build Profile targeting Meta Quest 3 with the correct scene list and scripting defines.

<figure><img src="/files/g877qlAq9hpd3Blqcs7y" alt=""><figcaption></figcaption></figure>

#### 2. Build Profiles > Android > ML2 Profile > Other Settings

Make sure the Vulkan Graphics API, ASTC texture compression format, package name, version, IL2CPP scripting backend, new input system, ARM64 target architecture, internal write permission, and application entry point are set correctly.

<figure><img src="/files/rD9u4MaB1s7UPU7cuCbT" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/EjDnG5G2Z31HuBZZtaXX" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/KK5h6smIKCVNSRsKzQCa" alt=""><figcaption></figcaption></figure>

#### 3. Build Profiles > Android > ML2 Profile > Publishing Settings&#x20;

Make sure the custom main manifest, custom main Gradle template, and custom launcher Gradle template are all correctly assigned.

<figure><img src="/files/M4Mfyq3bn2icjSdg9Lmf" alt=""><figcaption></figcaption></figure>

#### 4. Project Settings > XR Plug-in Management

Enable the OpenXR Plugin and Meta Quest feature group.

<figure><img src="/files/cJBOb3Zfem6lAdGhzinW" alt=""><figcaption></figcaption></figure>

#### 5. Project Settings > XR Plug-in Management > OpenXR > Enabled Interaction Profiles & Feature Groups

Check that any required interaction profiles, feature groups, and subsystems are enabled.

<figure><img src="/files/iAJXrdcXf3R5CoxzDGxP" alt=""><figcaption></figcaption></figure>

#### 6. Project Settings > XR Plug-in Management > Project Validation

Review that all *desired* checks pass successfully.

{% hint style="danger" %}
If you are using the **Marker Tracker** feature, it is necessary to leave some checks **unfixed.**
{% endhint %}

<figure><img src="/files/rfce8LO4fGyCEjggK25i" alt=""><figcaption></figcaption></figure>

If you are not using any of our features, like marker tracking, this should be alright:

<figure><img src="/files/TyVIuR7dfZHaS27V8j6u" alt=""><figcaption></figcaption></figure>

## Installing an App to Meta Quest 3

1. To install an .apk to your device, enable [Developer Mode](https://developers.meta.com/horizon/documentation/native/android/mobile-device-setup/#enable-developer-mode).
2. Connect your Meta Quest 3 to your computer using the Link Cable.
3. Enable "Allow USB debugging" if prompted.
   1. Check "Always allow from this computer" to not receive this popup in the future.
4. Use [SideQuest](https://sidequestvr.com/setup-howto) to install the app. Click "Install APK" and select your .apk file.

## Settings & Permissions on Device

For each app you download, you may have to manually grant permissions (e.g., camera, passthrough, hand tracking) in `Quick Settings > Passthrough`, `Settings > Camera`, and `Settings > Movement Tracking`.

Some app features require `Settings > Advanced > Developer Mode` to be enabled.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.meshmap.com/unity-sdk/xr/cross-platform-management/meta-quest-3.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.