> For the complete documentation index, see [llms.txt](https://developers-apps-in-toss.toss.im/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers-apps-in-toss.toss.im/guide/en/operation/deploy.md).

# Launch a Mini App

### 1. Pre-check

#### 1-1) Game and non-game release guide

Be sure to check the review guide and checklist before release. [Game](https://developers-apps-in-toss.toss.im/checklist/app-game)·[Non-game](https://developers-apps-in-toss.toss.im/checklist/app-nongame) Please check all the release guides to make sure development is complete. If you don't follow the guides, your submission may be rejected during review.

#### 1-2) Notes when uploading an app bundle

You can upload app bundles only if they are 100 MB or less uncompressed. If you include all resources such as images, sounds, and videos, the size may exceed the limit, so please manage resource files separately from the build.

We recommend managing resources like this.

* Include only the minimum resources required to run the app in the bundle.
* Configure large resources to be downloaded from external storage or a CDN.
* Applying a step-by-step download method (Lazy Loading) for additional resources improves the user experience.

<figure><img src="/files/9b8629255eb813c26a1f5477ce69ce922e927def" alt=""><figcaption></figcaption></figure>

***

### 2. Request review

After testing, press the 'Request review' button in the console to start the review. The review can take up to 3 business days, and depending on the app category, it may take 7 days or more.

* You must complete testing at least once before the review request button is enabled.
* Only one version can be submitted at a time for review.

If you find a bug to fix after requesting review, cancel the review by pressing the 'Cancel request' button. Then upload the new bundle (`.ait`) and request review again.

<figure><img src="/files/7384f18cd2d7b4b3c382f52f9fa1d01a29c30412" alt=""><figcaption></figcaption></figure>

#### If the review is rejected

After checking the reason by pressing the 'View rejection reason' button, upload a new bundle that fixes the issue and request review again. If you have more questions about the rejection reason, [Channel Talk](https://apps-in-toss.channel.io/workflows/787658)you can contact us at

***

### 3. Release

When the bundle is approved, we'll notify you of the review result by email. After that, press the 'Release' button in the console to make the mini app available to users.

Once released, it is applied to all users immediately. Be sure to test thoroughly before releasing.

<figure><img src="/files/6978c709ee8d9607fc1573274792b6d4a3eeb749" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**Differences between the test environment and the live environment**

The test environment and the actual live environment may have different CORS policies and network behavior. In particular, be sure to check the following features again in the live environment.

* Memory and resource usage
* Network requests (CORS): You must add the following domains to the Origin allowlist.\
  It varies by SDK version.<br>

  SDK 3.x

  * Production environment: `https://<appName>.web.tossmini.com`
  * QR test environment: `https://<appName>.private-web.tossmini.com`

  \
  SDK 1.x \~ 2.x

  * Production environment: `https://<appName>.apps.tossmini.com`
  * QR test environment: `https://<appName>.private-apps.tossmini.com`
* Permission handling
* Login and session persistence
* Real payment and authentication features

Even if it works normally in the test environment, errors may occur in the live environment.
{% endhint %}

***

### 4. Manage after release

After release, you can manage versions and updates in the Appintos console. Depending on your needs, you can upload a new bundle or maintain and manage the existing version.

#### 4-1. Deploy a new version (update)

* If you add new features or fix bugs, upload a new app bundle (`.ait`) just like before.
* The uploaded bundle goes through the review request → approval → release steps again.
* After approval, pressing the 'Release' button will replace the existing app with the new version.

Released versions are reflected to users immediately, so please test thoroughly beforehand before uploading.

#### 4-2. Roll back

* You can check the list of previously released versions in the 'App Release' menu.
* If a problem occurs, you can roll back to a previous version.
* Select the version to roll back to, then press the 'Release' button.

Rollback is also applied to users immediately, so please choose the version carefully.

<figure><img src="/files/1fd89893a6026305a2d688bebd3f7640ca254ead" alt=""><figcaption></figcaption></figure>

#### 4-3. Emergency fix (hotfix)

If a serious error occurs when running the app, [Channel Talk](https://apps-in-toss.channel.io/workflows/787658)please contact us immediately. We respond quickly in urgent situations.

#### 4-4. Post-release monitoring

Right after release, unexpected errors or performance issues may occur. We recommend monitoring the following items:

* Major error logs and crash logs
* Sentry monitoring via Sentry configuration
* API response latency and failure rate
* User feedback and usability issues
  * You can collect user feedback through the 'Report' feature in the navigation bar.
  * Submitted feedback can be viewed in the console's 'Reports' menu.
* Issues with delays or failures in loading external resources or CDN content

#### 4-5. Post-release inspection

Appintos continues reviewing mini apps even after release to provide users with a high-quality mini app experience. If post-release inspection identifies areas that need improvement, we may ask you to make improvements. If any legal or policy violations are found, emergency suspension may be carried out first in accordance with the operating policy.


---

# 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://developers-apps-in-toss.toss.im/guide/en/operation/deploy.md?ask=<question>&goal=<endgoal>
```

`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.