> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/release-notes/mobile/android/older/android-version-16.7.10.md).

# Android Version 16.7.10

### Features

* **AN-7909**: New and improved search which matches iOS, Web Vault, Desktop App and Browser Extension algorithm.

### Bug Fixes

* **AN-7892**: Android is not receiving changed logout timer from iOS
* **AN-7397**: If User A shares a record with a linked address or payment card to User B, User B cannot see the address or card fields.
* **AN-7946**: Cannot open files of office types, such as .doc or .xls
* **AN-7988**: KeeperFill prompt to enable is not appearing for Enterprise users
* **AN-7490**: Auto-suggestion fixes
* **AN-7581**: If a user changes a typed record (via Edit) that contains a TOTP field to a type that doesn’t have a TOTP field (in template), the record does not appear with the TOTP filter applied to the vault.

### Security Updates

* **AN-7932**, **AN-7933**: Security improvements found by Bugcrowd researchers


---

# 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://docs.keeper.io/release-notes/mobile/android/older/android-version-16.7.10.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.