> For the complete documentation index, see [llms.txt](https://docs.sprinto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinto.com/monitors/dr.-sprinto-and-manual-inputs/how-to-troubleshoot-dr.-sprinto-installation-on-apple-devices-running-apple-silicone-m1-m2-chips.md).

# How to troubleshoot Dr. Sprinto installation on Apple devices running Apple Silicone (M1 M2 chips)

If you are installing Dr. Sprinto on an Apple device running Mac OS, you need to have Rosetta installed on your device to run the Dr. Sprinto app.

Follow the below steps to install Rosetta on your device:

* Open Terminal. Press **Cmd + Space** to open the search bar, then look for the terminal.
* Enter the following command on the terminal and press enter.

  ```
  softwareupdate --install-rosetta
  ```
* Follow the on-screen instructions to install Rosetta on your device.

Once you have installed Rosetta, proceed with Dr. Sprinto installation on your device.&#x20;

If you still face issues with the installation or operations of Dr. Sprinto, please get in touch with [Sprinto support](mailto:www.support@sprinto.com).


---

# 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.sprinto.com/monitors/dr.-sprinto-and-manual-inputs/how-to-troubleshoot-dr.-sprinto-installation-on-apple-devices-running-apple-silicone-m1-m2-chips.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.
