> 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/jp/mobile/apple-ios/older/ios-version-16.7.0.md).

# iOS Version 16.7.0

## Features

* **IOS-6547:** Support for Brave browser
* **IOS-6559:** Siri Shortcuts for Keeper

See the user guide for more info:

[iOS User Guide](/user-guides/jp/ios.md)

## Bug Fixes

* IOS-6573: Crash when deleting a file from a record containing 10+ file attachments
* IOS-6574: Unable to use password zoom on v3 record when the record doesn't contain a login
* IOS-6440: File download is being called for individual files instead of as a batch operation
* IOS-6535: Record search is slowed when utilizing autofill
* IOS-6527: UI issues with 2FA options upon resuming an expired session
* IOS-6589: Translations missing for record TOTP menu


---

# 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/jp/mobile/apple-ios/older/ios-version-16.7.0.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.
