> 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

If you've finished final testing in the Toss app, you can request a review in the Apps in Toss console and launch the mini app.

### 1. Pre-checks

#### 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 both release guides and make sure development is complete. If you do not follow the guide, your submission may be rejected during review.

#### 1-2) Notes when uploading app bundles

You can upload only app bundles that are 100 MB or less after decompression. 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 lazy loading for additional resources improves the user experience.

<figure><img src="https://941686070-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8pQgXiR5QAzduV54W8Om%2Fuploads%2FvaJm4N1VhruvHhi7QH9z%2F%E1%84%87%E1%85%A5%E1%86%AB%E1%84%83%E1%85%B3%E1%86%AF%20%E1%84%8C%E1%85%B5%E1%86%A8%E1%84%8C%E1%85%A5%E1%86%B8%20%E1%84%8B%E1%85%A5%E1%86%B8%E1%84%85%E1%85%A9%E1%84%83%E1%85%B3%20%E1%84%92%E1%85%A1%E1%86%AF%20%E1%84%84%E1%85%A2%2097.png?alt=media&amp;token=3eca711d-0bcf-4c52-9d4c-d2856ef962cb" alt=""><figcaption></figcaption></figure>

***

### 2. Request review

After testing is complete, 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 more than 7 days.

* You must complete testing at least once before the Request review button becomes active.
* Only one version can be submitted per review request.

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

<figure><img src="https://941686070-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8pQgXiR5QAzduV54W8Om%2Fuploads%2FcsUExLlWzp8RoFEXz43x%2F%E1%84%87%E1%85%B5%E1%84%80%E1%85%A6%E1%84%8B%E1%85%B5%E1%86%B7%2083.png?alt=media&amp;token=1440e524-a2bc-45cc-8e55-7fee2c472479" alt=""><figcaption></figcaption></figure>

#### If the review is rejected

Click the 'View rejection reason' button to check the reason, then upload a new bundle with the issue fixed 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

Once the bundle is approved, we will notify you of the review result by email. Then, when you click the 'Release' button in the console, the mini app will become available to users.

When you release it, it will be applied to all users immediately. Be sure to test thoroughly before releasing.

<figure><img src="https://941686070-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8pQgXiR5QAzduV54W8Om%2Fuploads%2F4hikUgHNPAGvvwKERub9%2F%E1%84%87%E1%85%B5%E1%84%80%E1%85%A6%E1%84%8B%E1%85%B5%E1%86%B7%2032.png?alt=media&amp;token=b753d8a1-2dd6-4393-ae53-bd3ae270ff0f" alt=""><figcaption></figcaption></figure>

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

The test environment and the actual live environment may differ in CORS policy and network behavior. In particular, please be sure to check the following functions again in the real environment.

* Memory and resource usage
* Network requests (CORS): You need to register the domains below in the Origin allowlist.\
  This depends on the 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
* Actual payment and authentication features

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

***

### 4. Managing after release

After release, you can manage versions and updates in the Apps in Toss console. Depending on your needs, you can upload new bundles or maintain and manage existing versions.

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

* If you added a new feature or fixed a bug, upload a new app bundle in the same way as before (`.ait`)
* The uploaded bundle goes through the review request → approval → release process again.
* After approval, clicking the 'Release' button replaces the existing app with the new version.

The released version is applied to users immediately, so please test thoroughly before uploading.

#### 4-2. Rolling back

* In the 'App release' menu, you can view the list of versions that have already been released.
* If a problem occurs, you can roll back to a previous version.
* Select the version to roll back to, then click the 'Release' button.

Rollbacks are also applied to users immediately, so please choose the version carefully.

<figure><img src="https://941686070-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8pQgXiR5QAzduV54W8Om%2Fuploads%2Fr4B2aVhF5yBdGqRDIWCZ%2F%E1%84%80%E1%85%A6%E1%84%8B%E1%85%B5%E1%86%B7%2063.png?alt=media&amp;token=8b3289c5-2d37-4950-a472-fe118125339b" alt=""><figcaption></figcaption></figure>

#### 4-3. Emergency fixes (hotfixes)

If a serious error occurs while the app is running [Channel Talk](https://apps-in-toss.channel.io/workflows/787658)please contact us right away.

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

Unexpected errors or performance issues may occur right after release. We recommend monitoring the following items in particular.

* Major error logs and crash logs
* Sentry monitoring through Sentry configuration
* API response delays and failure rates
* User feedback and usability issues
  * You can receive user opinions through the 'Report' feature in the navigation bar.
  * Submitted feedback can be viewed in the 'Report history' menu in the console.
* Delays or failures when loading external resources or CDNs

#### 4-5. Post-release review

To provide users with a high-quality mini app experience, Apps in Toss performs mini app reviews even after release. If post-release review identifies areas that need improvement, we may request improvements. If a violation of laws or policies is discovered, an emergency suspension may be carried out first in accordance with the operation 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.