# How to Submit API 35 Version App Update to Google Play Store

***

This guide explains how to update your app to target API level 35 on the Google Play Store.

**Important:**

This process must be completed by Swing2App users directly. 

After updating the app, you must submit it via the Google Play Console.

If you're unable to submit it yourself, you may request an upload service from Swing2App. 

We will handle the entire process for you.

Please refer to the following guide on how to request a Play Store upload.

{% hint style="info" %}

### \[How to Request a Play Store Upload]

1.Go to the 'Maker' screen and update your app first.

[Refer to the App Update Guide.](https://documentation.swing2app.com/manual/v3/step4-complete-app-creation/how-to-update-an-app)

(If you've already updated, you can proceed to step 2 to purchase a ticket and submit your upload request.)

2.Purchase a Play Store upload ticket. ($20/1 time)

[Ticket Purchase Page](https://www.swing2app.com/view/order_info_action?product_id=4) (If you already have a ticket, skip to step 3.)

3.Go to [**Manager> Manage Version> Product History**](https://www.swing2app.com/view/app_work_history), and click **\[Play Store Upload]** to request the upload.

If there are any modifications (e.g. app description, screenshots), please edit them before submission.

If not, simply click "Submit" to proceed.
{% endhint %}

***

## **1. App Update**

{% hint style="success" %}
Please update your app via the Swing2App creation system.

The Swing2App platform now supports API level 35.

To reflect this update, users must rebuild their app and submit the new version to the Play Store.
{% endhint %}

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

1\)Go to the 'Maker' screen.

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

2\)Click the **\[App Update]** button on the top right.

3\)Check the "No Update Message" and click **\[Make]**.

<mark style="color:red;">For Push Apps: Select</mark> <mark style="color:red;"></mark><mark style="color:red;">**"No Update Message"**</mark><mark style="color:red;">.</mark>

{% hint style="warning" %}
**For WebView Apps: No popup appears during update, so no selection is needed.**

Q. Why can’t I select the update option for WebView apps?

A. WebView apps do not show update popups in the app, so the option is not necessary.
{% endhint %}

📢For **General Prototype Apps**:

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

-Update Type: Select **"Hard Update (App Re-install)"**.

-Update Message Option: Select **"No Update Message"**.

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

After starting the update, go to [**Manager> Manage Version> Product History**](https://www.swing2app.com/view/app_work_history)**.**

App creation may take up to 10 minutes. Once completed, the '**Get AAB File'** button will be activated.

Download the AAB file and proceed to the Google Play Console.

***

## **2.Google Play Store App Update Submission**

Go to the [Google Play Console](https://play.google.com/console/u/0/developers)

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

1\)Select the app you want to update.

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

2\)Go to **Testing & Release > Production**.

3\)Click **Create New Release**.

<figure><img src="/files/2aeji7XXSN6tiEomNxFp" alt=""><figcaption></figcaption></figure>

4\)In the **App Bundle** section, click **\[Upload]** and select your AAB file.

#### How to get your AAB file:

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

* Go to  [**Manager>Manage Version> Product History**](https://www.swing2app.com/view/app_work_history)**.** and click **\[Get AAB File]**.

{% hint style="danger" %}
**Important**

* If your original release used an APK file → continue using APK.
* If it used an AAB file → continue using AAB.\
  The update file type must match the original release format (APK or AAB).
  {% endhint %}

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

5\)In the **App Bundle** section, click **\[Upload]** and select your AAB file.

After uploading, check that:

* **API Level** is listed as **21 or higher**
* **Target SDK** is listed as **35**

Then click **Next**.

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

6\)Click **Save**.

7\)Click **Go to Overview**.

{% hint style="info" %}
Warning messages may appear. You can ignore them unless they are marked as "Error".
{% endhint %}

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

8\)Click **"Send OO changes for review"**

\*The number of changes may vary depending on your app.

9\)Make sure the status changes to **"In Review"**.

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

If the status remains as **"Ready to Submit"**, your app was not submitted properly.&#x20;

Go to the **Release Overview** and complete the submission.

Now, wait for the review process to complete.

{% hint style="success" %}
-Reviews usually take 1–2 days but may take up to 7 days.

-Once approved, the app update will be released.

-If rejected, you’ll need to check the rejection reason and submit a revised version.

You can check the production release status on the "Release Overview" page.

If you see messages like **"Update Rejected"**, **"Update Denied"**, or **"App Removed"**, it means the update was rejected.&#x20;

Please review the Google rejection message and take the necessary actions.
{% endhint %}

***

## **3.API 35 Policy Violation Resolved Message**

<div align="left"><figure><img src="/files/nzLtGDhruo88zniSzsGb" alt=""><figcaption></figcaption></figure></div>

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

After your app is updated, you should see a message indicating the policy issue is resolved.

Check for the message:

> *"Your app must target Android 15 (API level 35) or higher – Issue resolved."*

This confirms that the API 35 compliance has been properly processed.

> Note: This message may take up to 24 hours to appear after the update.\
> If it doesn’t appear immediately, please wait a day and check again.

***

This guide is for users who want to submit the app update to the Play Console themselves.

If you'd prefer not to handle it yourself, you can request an upload service from Swing2App.

Refer to the **Play Store Upload Request Guide** above for help.

{% hint style="info" %}

### \[How to Request a Play Store Upload]

1.Go to the app creation screen and update your app first.

[Refer to the App Update Guide.](https://documentation.swing2app.com/manual/v3/step4-complete-app-creation/how-to-update-an-app)

(If you've already updated, you can proceed to step 2 to purchase a ticket and submit your upload request.)

2.Purchase a Play Store upload ticket. ($20/1 time)

[Ticket Purchase Page](https://www.swing2app.com/view/order_info_action?product_id=4) (If you already have a ticket, skip to step 3.)

3.Go to [**Manager> Manage Version> Product History**](https://www.swing2app.com/view/app_work_history), and click **\[Play Store Upload]** to request the upload.

If there are any modifications (e.g. app description, screenshots), please edit them before submission.

If not, simply click "Submit" to proceed.
{% endhint %}


---

# 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://documentation.swing2app.com/store/playstore/api35.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.