> For the complete documentation index, see [llms.txt](https://developers.didomi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.didomi.io/cmp/mobile-sdk/vega-os/versions.md).

# Versions

#### 0.3.0 (Aug 14th, 2026) <a href="#id-2.30.0-september-17-2025" id="id-2.30.0-september-17-2025"></a>

* Upgrade to Vega SDK 0.24 and React Native 0.83. Apps should move to the stable Amazon packages (`react-native-kepler` 4.0.1, `webview` 4.0.2) and declare Vega OS 1.2 in their manifest.

#### 0.2.2 (Jun 25th, 2026) <a href="#id-2.30.0-september-17-2025" id="id-2.30.0-september-17-2025"></a>

* fix: `isCMPDisplayed` staying stuck after `preferences.hidden`. Notice and preferences visibility are now tracked independently and the displayed state is derived from both, so the CMP hides correctly when preferences close and stays visible when navigating back from preferences to the notice.
* fix: setCurrentUserStatus now performs partial consent updates

#### 0.2.1 (May 22nd, 2026) <a href="#id-2.30.0-september-17-2025" id="id-2.30.0-september-17-2025"></a>

* fix: preferences screen back navigation handling

#### 0.2.0 (May 6th, 2026) <a href="#id-2.30.0-september-17-2025" id="id-2.30.0-september-17-2025"></a>

* fix: missing mehods `notice.hide` and `preferences.hide`
* Add `onNoticeClickDisagree` event callback and improve `onError` callback
* fix: existing `click` events are incorrectly triggered

#### 0.1.0 (April 23rd, 2026) <a href="#id-2.30.0-september-17-2025" id="id-2.30.0-september-17-2025"></a>

* fix: inconsistent skdPath set by default

#### 0.0.2 (October 1st, 2025) <a href="#id-2.30.0-september-17-2025" id="id-2.30.0-september-17-2025"></a>

**Features:**

* Official release: upgrade to the latest Amazon Vega libraries


---

# 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://developers.didomi.io/cmp/mobile-sdk/vega-os/versions.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.