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

# Version 10.2.0 Changelog (June 21, 2023)

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

Version: 10.2.0

Release Date: June 21, 2023

## Notes

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

## Xamarin.Android

### New features

* Adds `ViewerConfig.Builder.MovableToolbarEnabled(bool)` to move annotation toolbar to left, right, and bottom edge of the viewer

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

* Adds `ToolManagerBuilder.SetInsertMultipleImagesEnabled(bool)` to add multiple image stamps to the viewer at a time

### Breaking changes

* Remove [PageCropper](https://www.nuget.org/packages/PDFTron.Android.PageCropper) if it is explicitly included in your NuGet package, otherwise no action is needed.

### Fixed

* Fix issue where view mode dialog is cutoff in phone landscape mode
* Fix issue where search would not restart when show/hide the full search result window
* Fix issue where on tablet signature selection dialog does not show up on first tap
* Fix issue where line ending style changes when select/deselect
* Fix potential crash when import XFDF to collaboration viewer when bbox is invalid
* Fix potential crash when rotating signature selection dialog when activity is recreated on orientation change
* Improve ReflowControl where show/hide toolbar will no longer change current viewport

## Xamarin.iOS

### New features

* The `PTThumbnailsSliderViewController` class is now marked as deprecated.
* Added additional German translations.

### Fixes

* The free text style settings in the `PTFreeTextInputAccessoryView`, shown above the keyboard while editing a free text annotation, are saved when the top bars (navigation bar) are hidden.
* Fixed a crash when a `PTPDFViewCtrl` is deallocated.
* Fixed a crash when selecting outside of a newly created text form field annotation while the form-creation tool is still active.
* Transparency is supported in signatures created from existing images.
* The annotation selection popup menu now has the same number of items after the style picker is dismissed.


---

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