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

# Version 6.7.2

Discover the latest updates in this release of the framework, including bug fixes and compatibility notes. Stay informed about the changes for iOS development. The Apryse iOS SDK streamlines secure do

Release Date: 2016.11.23

\##Framework changes:

* The framework targets iOS 8+. Note that the tools still require iOS 9+ due to using APIs only available in iOS 9+, but that old versions of the tools may be used with the new version of the framework after updating PDFNet APIs.

\##Bug fixes:

* In the tools, the popup for sticky notes now points to the correct location.
* Fixes a potential crash when optaining a `PTPoint` from a `PTQuadPoint`, and disposing of the `PTQuadPoint` before the `PTPoint`.


---

# 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-2.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.