> For the complete documentation index, see [llms.txt](https://legacy-docs.usesmileid.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://legacy-docs.usesmileid.com/further-reading/known-issues.md).

# Known Issues

## A. Summary of Issues

| Issue                                                                             | What is Affected     | Issue Type    | Description                                                                                                                                       |
| --------------------------------------------------------------------------------- | -------------------- | ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Agent Mode UI Quirk](#1-agent-mode-ui-quirk)                                     | Android-powered SDKs | UI Bug        | The overlay for agent mode does not completely fill the bottom of the screen on some small Android devices.                                       |
| [Compatibility with Play Store Devices](#2-compatibility-with-play-store-devices) | Android-powered SDKs | Functionality | Android SDKs may not work as expected on devices that do not support Google Play Services, causing crashes for face and document functionalities. |

## B. Issue Details

### 1. Agent Mode UI Quirk

* **Issue:**\
  The overlay with the oval face cutout does not fill the bottom of the screen. This leaves a small gap between the overlay and the navigation bar.
* **Screenshot:**\
  ![Agent Mode Capture](/files/YoMvdEyc8BDpX2De7QEZ)
* **Causes:**\
  The exact cause is unknown, but this issue has only been observed on small-screen Android devices (e.g., Neon Ray Pro 5.5”).
* **Possible Resolution:**\
  A resolution has not yet been found.

***

### 2. Compatibility with Play Store Devices

* **Issue:**\
  When users of our SDK utilize devices that do not support Google Play Services (for instance, some Huawei devices), the Android SDKs might not work as expected. This can result in crashes when attempting to use face and document functionalities.
* **Causes:**\
  This is because we rely on certain models from Google Play Services at build time, and devices that do not support Play will not download these models as needed.
* **Possible Resolution:**
  * We advise using a bundled version of ML Kit. [See Note in Android Initialisation section](/integration-options/mobile/getting-started.md#initialization)
  * Use the hosted-web (web embed) solution on mobile as a fallback.

***


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://legacy-docs.usesmileid.com/further-reading/known-issues.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.