> 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/older/ios-version-14.10.2.md).

# iOS Version 14.10.2

Released June 23, 2020

## Benefits & Enhancements

* **Increase Tappable Area of Custom Field Eye Icons** - The tappable area of the eye icon of custom fields values has increased in size to improve the user's accessibility to its masking/unmasking functionality.

## Bug Fixes

* **Fixed:** The payment dialogue for expired paid accounts closes immediately after opening, preventing the user from entering their payment information.
* **Fixed:** The share screen freezes when a new user attempts to share a record after they have verified their email address as directed.
* **Fixed:** Select QR codes are unable to be scanned for two-factor authentication.
* **Fixed:** Retry upload prompt causes crash (iPad only).
* **Fixed:** Various design and alignment issues.


---

# 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/older/ios-version-14.10.2.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.