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

# Version 11.7.0 Changelog (August 20, 2025)

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

Version: 11.7.0

Release Date: August 20, 2025

## Notes

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

## Xamarin.Android

### New

* Now targeting .NET 9 Android 15

### Fixes

* Fixed issue where fraction precision preset was incorrect for new installs
* Fixed issue where quick menu did not appear when text markup annotations are created through long press

## Xamarin.iOS

### Fixes

* Fixed behaviour where annotation wasn't updating on viewer in measurement unit & precision adjustments on measurement annotations while style picker is open
* Fixed issue where free text annotation was invisible when making changes to text directly


---

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