> 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-56298.md).

# Version 6.7.3.56298 (February 23rd, 2017)

Discover the latest updates for PTPDFViewCtrl, including bug fixes and enhancements. Learn more about the release date and improvements made with Xcode 8.2. The Apryse iOS SDK streamlines secure docum

Release Date: February 23rd, 2017 Built with Xcode 8.2

\##Bug fixes:

* PTPDFViewCtrl maintains page view mode during rotation when in continuous mode.
* Search highlights will now be maintained when changing pages.
* PTPDFViewCtrl will no longer (on rare occasions) become momentarily unresponsive after zooming a document while it was rendering.
* Tools no longer allow user to resize line annotations off the page.
* Various other minor bug fixes.


---

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