> 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/ios-build-not-showing-in-testflight.md).

# iOS Build Not Showing in Testflight

Apps are typically available to view in Testflight within 15 minutes after the Build is completed. Occasionally, you may not be able to view the newest build and will need to wait up to 2 hours to see the app in Testflight. You will receive an email from Apple when the app is ready for testing. 

#### Possible Causes:

1. Adalo’s Publishing could be temporary down.
2. Apple’s Publishing service could be temporary down.

#### Resolution:

1. Check the [Adalo Status](https://status.adalo.com/?utm_term=\&utm_campaign=*KB+-+Search+-+Create,+Develop,+%26+Build\&utm_source=adwords\&utm_medium=ppc\&hsa_acc=4913569088\&hsa_cam=20002976134\&hsa_grp=148203983277\&hsa_ad=655528080898\&hsa_src=g\&hsa_tgt=dsa-19959388920\&hsa_kw=\&hsa_mt=\&hsa_net=adwords\&hsa_ver=3\&gad=1\&gclid=CjwKCAjwrranBhAEEiwAzbhNtXDIe4epgig0spDRz9mrSiFPk4IARrt_AEA15ukErl5XKnGx7GITvBoCycQQAvD_BwE) Page.
2. Check the [Apple Status](https://developer.apple.com/system-status/) Page.
3. Wait 2 hours and push a new build. 

### **Still Need Help?**

If you're stuck, don't worry! Reach out to our [support team ](https://info.adalo.com/submit-a-support-ticket)for further assistance with the details below.

1. Include Steps Taken: Let us know what troubleshooting steps you've already tried.


---

# 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/ios-build-not-showing-in-testflight.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.