> 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-12/v12-1-0.md).

# Version 12.1.0 Changelog (August 19, 2026)

View the changelog the 12.1.0 for Xamarin

## Notes

This Apryse release for Xamarin brings the core PDF functionality and iOS and Android Tools functionality in line with version 12.1.0 of the iOS and Android SDKs.

## Xamarin.Android

### Breaking

* The timestamp displayed in the annotation list now displays creation time to match other Apryse SDK platforms such as Web and iOS.
* Annotation list author will now display the author name instead of ID if set.

### New

* Adds ability to read notes from caret annotation type.
* Adds support for `PDFViewCtrl` page-space geometry snapping.

### Fixes

* Fixed an issue where delete on page and delete all showed in the annotation list when permission checks are enabled.
* Fixed an issue where the date displayed in the annotation list had a timezone that did not match other Apryse SDK platforms such as Web and iOS.
* Improved accuracy for measurement tool snapping feature.

## Xamarin.iOS

### New

* Added support for `PDFViewCtrl` page-space geometry snapping.

### Fixes

* Fixed an issue where callout annotation bounding box was not properly calculated given negative coordinates.
* Fixed callout annotation opacity styling.
* Fixed an issue where JavaScript buttons on documents caused the entire viewer to re-render.
* Improved preset bar visibility in Liquid Glass.
* Fixed localization of a page indicator's "x of y" string to Danish and other languages.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.apryse.com/xamarin/changelogs/version-12/v12-1-0.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.