> For the complete documentation index, see [llms.txt](https://help.zipcaptions.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.zipcaptions.app/known-issues/ios-devices-give-an-error.md).
# iOS Devices Give an Error
If you are using an iOS device and you get the error:
> Speech recognition error: The user agent disallowed the requested speech recognition service, either because the user agent doesn't support it or because of reasons of security, privacy or user preference.
You need to enable the **Speech Recognition Engine** in the device settings. To do this:
1. Go to Settings\ 
2. Go to Privacy & Security\
3. Choose Speech Recognition\
4. Ensure that the toggle that is next to your browser is **Green**
5. Go back to **Settings** > **General** > **Keyboard**\
6. Scroll down until you get to **Dictation**\
7. Disable dictation by sliding the green toggle\
8. Now **re-enable dictation** by **sliding the slider** across again, and **choosing Enable in the prompt** which appears\
9. Return to Zip Captions, and your captioning should now work
---
# 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.zipcaptions.app/known-issues/ios-devices-give-an-error.md?ask=&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.
