> For the complete documentation index, see [llms.txt](https://support.8seats.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.8seats.com/troubleshooting/did-your-app-crash.md).

# Did your app crash?

Step-by-step guide

### My app crashed

If the app crashed, this may be caused by a variety of possible reasons. Our team reviews app crash reports regularly to help identify and resolve issues – and we frequently release updates to the app with new improvements and the latest fixes.

**What to do**

* Ensure that you have an active internet connection – follow the steps [here](#solution-1-check-your-internet-connection) if you need.
* If you’re using the mobile app, close the app completely and restart the app on your device.
* If you’re using the app in your web browser, refresh your browser (usually by pressing **Ctrl + R** on Windows/Linux, or **Command + R** on Mac).
* In some cases, you may need to sign back in to your 8seats account.
* Please ensure that you have the latest version of the app installed.

If you need further support from one of our team members you can always contact us. We're happy to help!

🤝 [Request Support](https://q2aas.share-ap1.hsforms.com/2JW-0IzD6R9y4WHBMJfwWKA)


---

# 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://support.8seats.com/troubleshooting/did-your-app-crash.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.