> 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/nfc-wallet-sdk-ios/help/knowledge-base/deploy-your-app-to-the-app-store.md).

# Deploy your app to the App Store

Use this checklist to deploy your iOS **digital wallet application** to the App Store.

For Apple’s end-to-end publishing flow, see [Submit your iOS and iPadOS apps to the App Store](https://developer.apple.com/ios/submit/).

### Before you begin

* Use the `Release` build of the NFC Wallet SDK.
  * See [Deliverables](https://docs.payments.thalescloud.io/nfc-wallet-sdk-ios/general/deliverables.md).
* Apply the release hardening guidance.
  * See [Security guidance](https://docs.payments.thalescloud.io/nfc-wallet-sdk-ios/security-and-privacy/security-guidance.md).
* Verify your iOS version support for the SDK release you ship.
  * See [Release notes](broken://spaces/6bUtiXdSFHu8lmOj8A0X/pages/MwBGLyxeVcwZWHlqCA4f) and [Mobile OS compatibility](https://docs.payments.thalescloud.io/nfc-wallet-sdk-ios/general/mobile-os-compatibility.md).

{% hint style="warning" %}
Do not upload an application that integrates the NFC Wallet SDK `Debug` build.

The `Debug` build is not allowed in the Production Environment.
{% endhint %}

### Deploy to the App Store

{% stepper %}
{% step %}

#### Prepare App Store Connect

Create or update the app record in App Store Connect.

Complete required metadata and privacy fields before submission.
{% endstep %}

{% step %}

#### Build and archive in Xcode

Archive a **Release** configuration build using Xcode Organizer.

Avoid shipping builds with debug symbols.
{% endstep %}

{% step %}

#### Upload and validate

Upload the archive using Xcode Organizer.

Fix any App Store Connect validation errors before testing.
{% endstep %}

{% step %}

#### Test with TestFlight

Distribute the uploaded build to internal testers first.

Run a full smoke test of provisioning and payment flows.
{% endstep %}

{% step %}

#### Submit for review

Submit the build for App Review from App Store Connect.

Monitor review feedback and resubmit if required.
{% endstep %}
{% endstepper %}

### Common release blockers

* Shipping the NFC Wallet SDK `Debug` build.
* Shipping a build that still logs sensitive data.
* Missing Apple approvals for contactless payment.
* Misconfigured entitlements or signing.

{% hint style="info" %}
If a store build behaves differently from your development build, capture device logs.

See [Retrieve logs from an iOS device](https://docs.payments.thalescloud.io/nfc-wallet-sdk-ios/help/knowledge-base/retrieve-logs-from-an-ios-device.md).
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.payments.thalescloud.io/nfc-wallet-sdk-ios/help/knowledge-base/deploy-your-app-to-the-app-store.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
