> For the complete documentation index, see [llms.txt](https://docs.snapfix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snapfix.com/how-the-apps-work/screens/account/device-blocked.md).

# Device blocked

{% hint style="info" %}
Draft, written by an agent and not yet checked by a person ([how to read these docs](https://docs.snapfix.com/how-to-read.md)). Platforms: iOS and Android. [Source on GitHub](https://github.com/snapfix/docs/blob/main/spec/screens/account/device-blocked.md).
{% endhint %}

Stops the app with a message when the device is jailbroken (iOS) or rooted (Android).

* **Where:**
  * iOS: at launch, before the [splash screen](https://docs.snapfix.com/how-the-apps-work/screens/account/splash.md), when `IOSSecuritySuite.amIJailbroken()` is true. The app delegate makes this screen the window's root and returns before it starts Survicate and the rest of the app (ios @ aa31967ac8, `Appdelegate/AppDelegate.swift:149-153`).
  * Android: from the splash's start, when `isDeviceRooted()` is true. The splash is not finished, so it stays underneath (android @ 86068bfeea, `SplashActivity.java:234, 419-422`).
* **Who:** anyone opening the app on a device that fails the check.
  * Android debug builds never show it: `isDeviceRooted()` returns false when `BuildConfig.DEBUG` is set.
  * A release Android build counts as rooted when the build tags contain "test-keys", or when `/system/app/Superuser.apk`, `/system/bin/su` or `/system/xbin/su` exists (`SplashActivity.java:200-228`). A rooted phone that hides these files passes.
* **Feature:** [App launch](https://docs.snapfix.com/product/features/account/app-launch.md)

## Layout

The Snapfix logo, the block message, and the app version at the bottom.

iOS message (`jailbreak_block_message`):

> Dear User,
>
> We have detected that your device is jailbroken.
>
> To ensure the security and stability of our application, we kindly request that you restore your device to its original, non-jailbroken state. This will allow you to continue using our application without any compatibility or security issues.
>
> Thank you for your cooperation.
>
> Best regards, Snapfix Team

Android message (`root_error_message`): the same text with "rooted" and "non-rooted", and a space after "Dear User,".

The version is "v." and the version on iOS ("v.6.10.82"), and "v. " and the version on Android ("v. 6.10.82").

## Inputs

None.

## Actions

None. The screen has no button or link.

## States

* **Loading:** none; the check is local and the message shows at once.
* **Empty:** not applicable.
* **Error:** the screen is itself the result of a failed check. There is no retry.
* **No permission:** the check asks for no permission.
* **Offline (mobile):** looks the same; nothing goes over the network.

## Platform differences

| Topic   | iOS                                | Android                                                                                       |
| ------- | ---------------------------------- | --------------------------------------------------------------------------------------------- |
| When    | Before the splash is created       | After the splash has started, on top of it                                                    |
| Check   | `IOSSecuritySuite.amIJailbroken()` | Build tags and the three files above; skipped in debug builds                                 |
| Wording | "jailbroken" / "non-jailbroken"    | "rooted" / "non-rooted"                                                                       |
| Version | "v." with no space                 | "v. " with a space                                                                            |
| Back    | Nothing to go back to              | System back closes the screen and shows the splash, whose start check opens this screen again |


---

# 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.snapfix.com/how-the-apps-work/screens/account/device-blocked.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.
