> 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-9/v9-1-2-78725.md). # Version 9.1.2 Changelog (December 13th, 2021) World's #1 PDF SDK Library for Web, Mobile, Server, Desktop * Versions: 9.1.2.78725, 9.1.2.78728 * Release Date: December 13th, 16th, 2021 * Built with Xcode 13.1 (13A1030d) ## 9.1.2.78725 ### New Features * Support for Annotation states (accepted, rejected, approved, not approved) in the annotation replies UI * Inserting new pages can now be done from the "Insert" toolbar * Support for drag-and-drop of images onto a PDF, which are added as stamps. * Imperial measurements are displayed in fractions of an inch rather than decimals. * Externally linked files with destination page numbers are now supported. * The arrow drawing direction has been reversed to conform with industry norms and Apryse's Android SDK. * New reflow UI options to control if scrolling is vertical or horizontal. ### New APIs * Ability to exclude specific annotation types from being removed by the `PTEraser` tool. * The `PTSmartPen` tool can now be enabled and disabled with the new `PTToolManager` instance property `isSmartPenEnabled`. * Whether to store the newly created signature or persist the setting can now be set in `PTSignatureAnnotationOptions`. * A new document-opening API was added to the `PTDocumentController` and `PTTabbedDocumentViewController` classes * The optional `PTDocumentOptions` parameter can be used to specify the file type/extension for files do not have an extension, or for files that have an incorrect extension ### Fixed * Restored API to turn off all images in reflow. * Annotations created by subclasses of tools in the Prepare Form toolbar can now be edited if the tool is active. * Fixed a rare crash that could occur when opening documents with a very large number of annotations. * Able to show signature list on the legacy `PTAnnotationToolbar`. * Improved performance of tabbed-viewer tab persistence. * Fixes an issue with closing tabbed-viewer tabs from the tab overview control. * Fixed issue where annotation replies could not be deleted in certain circumstances. ## 9.1.2.78728 ### New APIs * Events are posted before and after text is copied from a document. Before the text is copied, it is possible to change the text (limit the number of characters, remove sensitive information, etc.). ### Fixed * Fixes an issue caused by a missing default (imperial) fraction precision for measurement annotations * Sets the default color of sticky note annotations to yellow instead of black * The eraser tool now erases freehand highlight marker annotations point-by-point, the same as freehand ink annotations --- # 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-9/v9-1-2-78725.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.