> 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-3-0.md).

# Version 10.3.0 Changelog (August 2, 2023)

World's #1 PDF SDK Library for Web, Mobile, Server, Desktop

Version: 10.3.0

Release Date: August 2, 2023

## Notes

This release of Apryse for Xamarin brings the core PDF functionality and iOS and Android Tools functionality inline with version 10.3.0 of the iOS and Android SDKs. More information can be found on [What's New for iOS](/ios/changelogs/version-10/v10-3-0.md) and [What's New for Android](/android/changelogs/version-10/v10-3-0.md).

## Xamarin.Android

### New features

* Adds the ability to move multiple pages together in the thumbnail viewer

![](https://653871032-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgjsBtuYmcKhWOdM9VCg4%2Fuploads%2Fgit-blob-039c999b1f36dc7bf8774c136719706bd1ab2438%2Ff9ab1e49ca45d5ef9f89a76123e2a7a24d68b536-600x1233.gif?alt=media)

### Breaking changes

* [`IPdfDocModificationListener`](https://sdk.apryse.com/api/xamarinandroid/tools/api/pdftron.PDF.Tools.ToolManager.IPdfDocModificationListener.html) now includes [`onPagesMoved`](https://sdk.apryse.com/api/xamarinandroid/tools/api/pdftron.PDF.Tools.ToolManager.IPdfDocModificationListener.html#pdftron_PDF_Tools_ToolManager_IPdfDocModificationListener_OnPageMoved_System_Int32_System_Int32_) callback

### Behavior changes

* `ToolManager.RichContentEnabledForFreeText(bool)` is now a global setting for the Free Text tool
* `ToolManager.SnappingEnabledForMeasurementTools(bool)` is now a global setting for measurement tools

### Notes

This release of Apryse for Android brings the core PDF functionality inline with version 10.3.0 of the Apryse cross-platform APIs. More information can be found on What's new for cross-platform APIs. Most non-module related changes apply to Android.

### Fixed

* Fix issue where the bookmark list is not updated when a new bookmark is added on tablets
* Fix crash where certain documents with OCG layers would throw an `ArrayIndexOutOfBoundsException`

## Xamarin.iOS

### New Features

* Added: API to set the default collapsed state of outline items in the `PTOutlineViewController`.

### Fixed

* Fixed: Image stamps become corrupted (grey) after cropping.
* Fixed: Crash when rotating after adding a highlight text markup annotation on phones.
* Fixed: Crash when selecting free text annotations with complex appearances.
* Fixed: Signature is not applied to signature field when switching from filling a text form field with the keyboard.
* Fixed: Annotation is visible when selecting from the annotation list on phones.
* Fixed: The keyboard dismisses while tabbing between text form fields.


---

# 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-3-0.md?ask=<question>&goal=<user_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.
