> For the complete documentation index, see [llms.txt](https://docs.sharinpix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sharinpix.com/faqs/how-to-record-the-screen-on-ios.md).

# How to record the screen on iOS?

If you are facing a problem on iOS using Salesforce mobile App, Salesforce Field Service Lightning App or even SharinPix App, it could be very helpful to capture your screen to show us what your problem looks like.

To do so, please follow those easy steps:

* Add Screen Recording to Control Center.
* Go to Settings > Control Center > Customize Controls, then tap the ( + ) icon next to Screen Recording.
* [Open Control Center](https://support.apple.com/kb/HT202769).
* Tap the Rec icon ( O ) , then wait for the three-second countdown. To capture sound while you record, press deeply on and tap Microphone Audio.
* To stop recording, [open Control Center](https://support.apple.com/kb/HT202769) and tap ( <i class="fa-rectangle-vertical">:rectangle-vertical:</i> ) . Or tap the red status bar at the top of your screen and tap Stop.

You can find your screen recording in the Photos app.

## More information from Apple help

<https://support.apple.com/en-us/HT207935>


---

# 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.sharinpix.com/faqs/how-to-record-the-screen-on-ios.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.