> 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/apple-ios/ios-version-17.2.0.md).

# iOS Version 17.2.0

Released April 21, 2025

### Enhancements:

* **iOS-7630**: You can now tap on file attachments to View, Save, or Delete Local Copy directly from the Record Details screen. Save files to your device, open them in other apps, or share them via Messages, WhatsApp, Airdrop, and more. Note: if your organization restricts file exports, certain actions may be limited.

<div><figure><img src="https://1549319098-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LSGErxSfzX6xZALob42%2Fuploads%2Fn7lq9uLI3RE5Mk7xuqIN%2Fattachment%20options.png?alt=media&amp;token=ab28c8d3-3c69-40e7-a8fb-38cb42f63faf" alt="" width="200"><figcaption></figcaption></figure> <figure><img src="https://1549319098-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LSGErxSfzX6xZALob42%2Fuploads%2FakbZb6Lapxs5vYkpIpis%2Fshare%20sheet.png?alt=media&amp;token=c467b6be-1af1-4613-b7e2-7ae7c81668a0" alt="" width="200"><figcaption></figcaption></figure></div>

### Bug Fixes:

* **iOS-7277**: Resolved a bug where adding a passkey to an existing record inside a folder caused the record to duplicate to the root directory. Users were unable to move the record back into the folder and received a “You do not have the required privilege” error. This issue is now fixed, and records can be moved as expected.
* **iOS-7350**: fixed an issue where users were stuck in an endless biometrics loop if biometrics failed and couldn’t be canceled. If biometrics failed, tapping "Cancel" would automatically prompt for biometrics again, preventing access. The fix ensures that after canceling, users can either try biometrics again or enter their master password.
* **iOS-7646**: Resolved an issue where files on V3 records were getting corrupted during decryption, causing errors when opened in external applications.
* **iOS-7619**: Fixed issue with the “Move To” button on the record details screen when the record resides at the vault level and is opened via search.
* **iOS-7580**: Addressed crash when the client has pending file uploads at login.
* **iOS-7575**: Updated reset password logic so users are properly logged out when utilized.
* **iOS-7552**: Resolved navigation to a record directly from a deep link when users are already logged in.
* **iOS-7304**: Addressed requirement on file and photo field that was preventing saving a custom record.
* **iOS-7277**: Fixed an issue where adding a passkey to an existing record that resides inside of a folder was causing unexpected results.
* **iOS-7649**: Updated search screen to display proper record location directly after a record has been moved.
* **iOS-7650**: Resolved the issue where a user could be presented a blank vault after their password was changed on a different device.
* **iOS-7652**: Minor design adjustment for password zoom sheet to address background color inconsistency.


---

# 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.keeper.io/release-notes/mobile/apple-ios/ios-version-17.2.0.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.