> For the complete documentation index, see [llms.txt](https://docs.sharinpix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sharinpix.com/release-notes/release-notes-q2-2022.md).

# Release Notes - Q2 2022

## Known Bug with correction

* SharinPix Mobile App : multiple rotation on annotation mode crash
* SharinPix Mobile App : Snap and Say available while microphone in ease
* SharinPix Mobile App : Torch button while taking pictures (permanent flash)
* SharinPix Album : Crash using Image Sync
* SharinPix Album : increase limit to 200 images for custom sort
* SharinPix in Iframe : Corrected History (back button supported)
* SharinPix to PDF : extra blank page removed
* SharinPix to Rich Text : Bad image alignement corrected

## Features

* New set of icons for Component
* SharinPix Mobile App : Sort menu also available on mobile
* [SharinPix Album : Annotation Toolbar personalisation](/documentation/features/user-interface/large-view-toolbar-annotate.md)
* SharinPix components : Icons as available on the Builders have changed
* [SharinPix Plan : Item List available on mobile](/documentation/lightning-web-component/sharinpix-plan.md)


---

# 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.sharinpix.com/release-notes/release-notes-q2-2022.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.