> For the complete documentation index, see [llms.txt](https://docs.payments.thalescloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payments.thalescloud.io/pin-management/integrate-d1-sdk/deployment/how-to-deploy-the-app-to-google-play-store.md).

# How to deploy the app to Google Play Store?

This section describes the steps on how to deploy the issuer application to Google Play Store, including the critical part of application signing using the correct certificate.

Let's start with the basics on how to create an app release on Google Play Store.

### Creating your app

1. Open the [Play Console](https://play.google.com/console/u/0/developers).
2. Select **All apps > Create app**.
3. Select a default language and add a title for your app. Type the name of your app as you want it to appear on Google Play Store. You can change the app name again later.
4. Specify whether your application is an app or a game. You can change the category again later.
5. Specify whether your application is free or paid.
6. Add an email address that Play Store users can use to contact you about this application.
7. Complete the “Content guidelines” and “US export laws” declarations.
8. Select **Create app**.

### Setting up your app

After the app is created, you can continue with its setup.

Your app’s dashboard will guide you through all the important steps to get your app available on Google Play Store.

You can start by providing details about your app’s content, by entering information for your Google Play Store listing.

Subsequently, move to the app release where it will guide you through pre-release management, testing, and promotion to build pre-release excitement and awareness.

The final step is launching your app on Google Play Store to make the app available to end users.

{% hint style="warning" %}
Starting August 2021, new apps will be required to publish with the Android App Bundle on Google Play Store.
{% endhint %}

### Uploading an app

1. Open the Play Console.
2. Select **All apps > select app**.

   You will be taken to the **Dashboard** page.

<figure><img src="/spaces/62lLFDcmLCeqqwmy4Fee/files/kLNieIxfr84VZ8c9A0hy" alt=""><figcaption><p>Play Console dashboard.</p></figcaption></figure>

3. On the left-side menu, select **Testing > Closed testing**.

<figure><img src="/spaces/62lLFDcmLCeqqwmy4Fee/files/suoG8yX3a6GoTnxDCQM8" alt=""><figcaption><p>Closed testing menu</p></figcaption></figure>

4. To create a new track, click **Create track**, enter the track name, and click **create new release**.

<figure><img src="/spaces/62lLFDcmLCeqqwmy4Fee/files/R179cfkIFNLqhSc0201c" alt=""><figcaption><p>Create a track and a release</p></figcaption></figure>

5. You can change the app signing preferences depending on whether you publish your app using the Android app bundle or APK.

{% tabs %}
{% tab title="App Bundle" %}
You can change the app signing preferences to **Export and upload a key from Java keystore**. Follow the on-screen instructions to make the update.

<figure><img src="/spaces/62lLFDcmLCeqqwmy4Fee/files/H703xFXkewL4fwMpFMTq" alt=""><figcaption><p>App signing preference for an Android App Bundle</p></figcaption></figure>
{% endtab %}

{% tab title="APK" %}
You can change the app signing preferences to "**Opt out of Play app signing**".
{% endtab %}
{% endtabs %}

6. Select the files to upload, depending whether you publish your app using the Android app bundle or APK.

{% tabs %}
{% tab title="App Bundle" %}
Select the app bundle to upload. After a successful upload, you will see the following app bundle:

<figure><img src="/spaces/62lLFDcmLCeqqwmy4Fee/files/L8cOiUKmxIkyzUoyCDWn" alt=""><figcaption><p>Uploaded Android App Bundle</p></figcaption></figure>
{% endtab %}

{% tab title="APK" %}
Select APKs (32 and 64 bit) to upload, after a successful upload, you will see the following APKs:

<figure><img src="/spaces/62lLFDcmLCeqqwmy4Fee/files/LcgleNYG9kFtDanZapyO" alt=""><figcaption><p>Uploaded APKs.</p></figcaption></figure>
{% endtab %}
{% endtabs %}

7. Enter the release name in **Release details** and click **Save**.
8. Click **Review release**, and you will see the release details on the next screen.

{% tabs %}
{% tab title="App Bundle" %}

<figure><img src="/spaces/62lLFDcmLCeqqwmy4Fee/files/QhKRf9gGH4cxcI2d1E7z" alt=""><figcaption><p>Review the Android App Bundle release</p></figcaption></figure>
{% endtab %}

{% tab title="APK" %}

<figure><img src="/spaces/62lLFDcmLCeqqwmy4Fee/files/ir2caZgb6jRXpAkaMfg3" alt=""><figcaption><p>Review the APK release.</p></figcaption></figure>
{% endtab %}
{% endtabs %}

9. Review your release and click **Start rollout to Mybank wallet alpha**.

<figure><img src="/spaces/62lLFDcmLCeqqwmy4Fee/files/VoD3VYeItCp8DJTy5H3M" alt=""><figcaption><p>Start the rollout</p></figcaption></figure>

10. Your app is now waiting to be reviewed. After the review, the app can be tested.

<figure><img src="/spaces/62lLFDcmLCeqqwmy4Fee/files/yRF93jkJyNuYImXu5RZ2" alt=""><figcaption><p>Release status is “In review”</p></figcaption></figure>


---

# 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:

```
GET https://docs.payments.thalescloud.io/pin-management/integrate-d1-sdk/deployment/how-to-deploy-the-app-to-google-play-store.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.