> For the complete documentation index, see [llms.txt](https://docs.apryse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apryse.com/ios/changelogs/version-6/v6-7-3-50420.md).

# Version 6.7.3

Discover the latest updates and bug fixes in this release from 2016.11.30. Enhancements include fixes for double tap to zoom, moving annotations, thumbnail control, and more. Stay up-to-date with our

Release Date: 2016.11.30

\##Bug fixes:

* Fixes a problem with double tap to zoom in some cases. This requires an update to the framework and the tools.
* Fixes a problem with moving annotations when in a continuous view mode on pages > 1 works correctly.
* Fixes a problem in the thumbnail control that would result in some thumbnails not showing up when run on iOS 10+.
* Fixes problem in the floating signature tool where the signature wasn't visible when being drawn.
* Fixes a problem where find text wouldn't reposition the view to show found text.
* Updates the Swift sample to properly resize during device rotation.


---

# 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.apryse.com/ios/changelogs/version-6/v6-7-3-50420.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.