> For the complete documentation index, see [llms.txt](https://help.adalo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.adalo.com/publishing-apps/publishing-to-the-apple-app-store/submit-your-build-to-the-app-store/build-error-you-have-already-reached-the-maximum-allowed-number-of-keys-for-this-service.md).

# Build Error: You have already reached the maximum allowed number of keys for this service

Although not common, you may have an iOS build fail if you have an existing notification key which we are unable to use during the build process.

#### Cause:

You have an existing Notification Key in your Apple Developer Account. Adalo requires one key for push notifications within iOS apps which cannot be opted out of. 

#### Resolution:

Remove any Notification Key in order for Adalo to be able to create one so that we are able to upload this app to TestFlight. To do this, please follow these steps:

1. Log in to your [Apple Developer Account](https://developer.apple.com/account/resources/authkeys/list).
2. Navigate to "Account"
3. Select "Certificates", then Identifiers and Profiles, then go to the left side and select keys.
4. Then revoke access on a key using Apple Push Notifications service (APNs).
5. Go back to Adalo and create a new build for your iOS app. This will generate a fresh key and you should be able to proceed.


---

# 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://help.adalo.com/publishing-apps/publishing-to-the-apple-app-store/submit-your-build-to-the-app-store/build-error-you-have-already-reached-the-maximum-allowed-number-of-keys-for-this-service.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.