---
title: App Store Publishing Troubleshooting
description: Fix common app store submission issues with Capawesome Cloud — failed submissions, TestFlight processing, App Review, and Google Play rejections.
---

# Troubleshooting

## First, try Ask AI

On any failed deployment, click **Ask AI** in the Console for a one-click diagnosis with the likely cause and a suggested fix. See [Cloud Assist → Ask AI](../assist/ask-ai.md).

## Submission not appearing in TestFlight

After a successful submission, Apple needs time to process the build before it shows up in TestFlight — this can take several minutes. If it still doesn't appear:

- Confirm the destination's **Team ID** and credentials are correct.
- Check that the build's version and build number are higher than any existing build.
- Review the deployment logs for an App Store Connect error.

## Deployment fails with "Info.plist must declare ITSAppUsesNonExemptEncryption"

Distributing to beta groups and submitting for App Review require your app's `Info.plist` to declare `ITSAppUsesNonExemptEncryption`. Capawesome Cloud doesn't answer Apple's export compliance question on your behalf, so the deployment fails before the upload. Add the key to your app's `Info.plist` (`ios/App/App/Info.plist` in a Capacitor project), commit the change, and rebuild before deploying again. Use `false` if your app only uses exempt encryption such as HTTPS; see Apple's guide on [complying with encryption export regulations](https://developer.apple.com/documentation/security/complying-with-encryption-export-regulations){:target="_blank"} if you are unsure, and the [prerequisites](submit-for-app-review.md#prerequisites) for App Review submission.

```xml
<key>ITSAppUsesNonExemptEncryption</key>
<false/>
```

## TestFlight deployment fails with "No changelog provided"

The App Store Connect destination has beta groups, which require release notes for **What to Test**, but the deployment has none. This happens when an [automation](submit-automatically.md) submits to such a destination, since automations can't provide release notes. Submit the build with [release notes](release-notes.md) instead, or remove the [beta groups](submit-for-app-review.md#distribute-to-beta-groups) from the destination.

## Release notes or App Review settings require an API key

Beta groups, **Submit for App Review**, and release notes only work with App Store Connect **API key** authentication. With an Apple ID and app-specific password, the Console doesn't offer these settings and the CLI and API reject them. Switch the destination's authentication method to `API Key` — see the [App Store Connect destination](destinations/apple-app-store.md#api-key-credentials).

## First App Store version fails with release notes

Apple rejects **What's New** on the very first App Store version of an app. Release notes only fail when the destination submits for review, since TestFlight's What to Test is unaffected. Deploy the first version without release notes, and Capawesome Cloud submits it without **What's New**. Or use a destination with **Submit for App Review** turned off and submit the version in App Store Connect yourself. See [First App Store version](submit-for-app-review.md#first-app-store-version).

## App Review submission failed

If the submission fails after the build was attached, the prepared App Store version stays in App Store Connect. Check the deployment logs for Apple's error, fix the cause, then submit the version in App Store Connect or deploy a new build. Capawesome Cloud only sets **What's New**, so make sure the rest of the App Store listing, such as the screenshots, is complete in App Store Connect. See [After a failed submission](submit-for-app-review.md#after-a-failed-submission).

## Google Play submission rejected

- For a brand-new app, the **first version must be uploaded manually** to the Play Console before automated submissions work.
- Confirm the service account has the required permissions in the Play Console.
- Check that the **package name**, **track**, and **release status** on the destination match your app.

## Still stuck?

Reach out via [Support](../../support/index.md) with a link to the failed deployment and its logs.