> 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-8/v8-1-1-76927.md). # Version 8.1.1.76927 Changelog (January 22nd, 2021) World's #1 PDF SDK Library for Web, Mobile, Server, Desktop * Version: 8.1.1.76927 * Release Date: January 22nd, 2021 * Built with Xcode 12.3 (12C33) Note, this release includes **64-bit slices only**, and supports iOS 11 and up. If you receive the error "Building for iOS Simulator, but the linked framework 'PDFNet.framework' was built for iOS", please change the build setting "Validate Workspace" to `YES`. The next version of Apryse for iOS will ship as an .xcframework, eliminating this requirement. ## New * Support for PDFs which start with a number other than 1, eg. i, ii, iii. This is useful with some professionally produced PDFs such as textbooks. ## Bug fixes * Resolves an issue where it was not possible to create free text annotations with a font size of less than \~12 pt. * Resolves an issue where using an Apple Pencil after the toolbars had been hidden would cause them to be shown. * Resolves an issue where view position after downloading a document view position would not be maintained in non-continuous page presentation modes. * Resolves an issue where freehand annotations could on rare occasions get saved to the wrong spot * Resolves an issue where returning `false` from `shouldSelectAnnotation` would cause the annotation to hide --- # 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-8/v8-1-1-76927.md?ask=&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.