> 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/xamarin/changelogs/version-10/v10-4-0.md). # Version 10.4.0 Changelog (September 13, 2023) World's #1 PDF SDK Library for Web, Mobile, Server, Desktop Version: 10.4.0 Release Date: September 13, 2023 ## Notes This release of Apryse for Xamarin brings the core PDF functionality and iOS and Android Tools functionality inline with version 10.4.0 of the iOS and Android SDKs. More information can be found on [What's New for iOS](/ios/changelogs/version-10/v10-4-0.md) and [What's New for Android](/android/changelogs/version-10/v10-4-0.md). ## Xamarin.Android ### Fixed * Fixed some form fields rendering with black background when selected. * Fixed `CollabManager.ImportAnnotations` not retaining custom appearance. * Fixed XML malform error when creating Rich-Content FreeText annotations. * Fixed annotation's orientation when moving annotation to rotated pages. * Optimized layout inflation when components are hidden in Viewer. ## Xamarin.iOS ### New Features * Added the ability to insert multiple images at once with image stamp tool. * The maximum thickness in the style picker on iPhones can now be controlled and overridden programmatically. * Removed the Apple Pencil freehand setting from the settings view. ### Fixed * Fixed the toolbar switcher's (`PTToolGroupIndicatorView`) alignment and spacing to be center-aligned. * Fixed the text color of callout annotations not updating after being set in the style picker. * Fixed a scroll-jump when changing (without lifting a finger) from a pan to pinch-zoom gesture. --- # 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/xamarin/changelogs/version-10/v10-4-0.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.