> For the complete documentation index, see [llms.txt](https://docs.coda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coda.co/codapay/in-app-payments/unity-sdk-internal-beta-testing-unity-native-integration/unity-sdk-internal-beta-testing-introduction/development-environment-setup-before-internal-beta-testing.md).
# Development Environment Setup Before Internal Beta Testing
## **1. Unity Hub Installation**
* **Download**: Unity Hub – [Official Download](https://unity.com/download)
* **Install** Unity Hub on your development machine.
* **Login to Unity Account**:
* **When**: Right after installing Unity Hub and launching it for the first time.
* **Why**:
* Required to activate your Unity license (even for the free Personal plan).
* Enables access to Unity services.
* **How**:
1. Launch Unity Hub.
2. Click **Sign In**.
3. Enter your Unity ID credentials or create a new account if you don’t have one.
4. If prompted, select the **Personal** license (for internal beta testing) and confirm eligibility.
* **Verification**: Launch Unity Hub and ensure you can access the **Installs** and **Projects** tabs.
## **2. Unity with Visual Studio and Android Build Support Installation (Unity 2020.3.48f1)**
* **Unity Version**: Install Unity 2020.3.48f1 for the internal beta testing from the [Official Download Page](https://unity.com/releases/editor/whats-new/2020.3.48f1) via Unity Hub
1. Click **Installs → Open Unity Hub**.
2. In **Add Modules**, check:
* Android Build Support
* Android SDK & NDK Tools
* OpenJDK
* IDE support (choose one):
* On **Windows**: Microsoft Visual Studio Community (with “Game development with Unity” workload)
* On **macOS**: Visual Studio for Mac
3. Click **Done** and wait for Unity Hub to finish the installation
**Configure Your Script Editor**
* In Unity Editor
* Windows: **Edit → Preferences → External Tools → External Script Editor** → **Visual Studio**
* macOS: **Unity → Preferences(Settings) → External Tools → External Script Editor** → **Visual Studio for Mac**
**Optional: Visual Studio Code Integration**
If you prefer **VS Code**:
1. Download & install VS Code from
2. In VS Code, install extensions:
* [C# (Microsoft)](https://marketplace.visualstudio.com/items?itemName=ms-dotnettools.csharp)
* [Unity(Microsoft)](https://marketplace.visualstudio.com/items?itemName=VisualStudioToolsForUnity.vstuc)
3. In Unity Editor → **Preferences → External Tools**:
* Set **External Script Editor** to your VS Code executable (`Code.exe` on Windows, `Visual Studio Code.app` on macOS).
* Under **“Generate .csproj and .sln files for:”**, enable all package types (Embedded, Local, Registry, Built-in).
4. Restart Unity so VS Code becomes the active script editor.
## **3. Android SDK Installation for Emulator**
* Download and install Android Studio from [here](https://developer.android.com/studio)
* Open the Android Studio, it will ask you to install Android SDK, keep following the instruction
* Go to Device Manager\
* Create a new virtual device
* Then start the virtual device by pressing on Play button on the virtual device item in the list, make sure to select Android API 36.0 or higher\
* You'll see the emulator running\
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## 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, and the optional `goal` query parameter:
```
GET https://docs.coda.co/codapay/in-app-payments/unity-sdk-internal-beta-testing-unity-native-integration/unity-sdk-internal-beta-testing-introduction/development-environment-setup-before-internal-beta-testing.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.