> 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-11/v11-5-0.md).

# Version 11.5.0 Changelog (May 28, 2025)

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

Version: 11.5.0

Release Date: May 28, 2025

## Notes

This release of Apryse for Xamarin brings the core PDF functionality and iOS and Android Tools functionality inline with version 11.5.0 of the iOS and Android SDKs.

## Xamarin.Android

### New

* Added APIs to define measurement units and precision array for measurement tools such as ruler, perimeter and area measurement tools: `AnnotStyleProperty.SetMeasurementPrecisions`, `AnnotStyleProperty.SetMeasurementBaseUnits`, `AnnotStyleProperty.SetMeasurementTranslateUnits`

## Xamarin.iOS

### New

* Exposed `hasChangesSinceSnapshot` API for improved adjustment of undo/redo
* Added the option to specify precision and measurement units for any measurement tools

### Fixes

* Fixed issue where the measurement snapping issue could not be disabled
* Fixed ruler annotations not being read as ruler annotations in the style picker title


---

# 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-11/v11-5-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.