Skip to main content

Changelog

0.17.2​

January 27, 2026

Summary​

Introduces user-specific consent storage to prevent cross-device consent contamination and comprehensive migration system for backward compatibility.

New Features​

  • User-specific consent storage isolation - Each user's consent is now stored separately using hashed user identifiers, preventing consent data from being shared between different users on the same device.
    Why it matters: Ensures privacy compliance by preventing one user's consent choices from affecting another user's experience on shared devices.

  • Automatic storage migration system - Seamlessly migrates existing consent data from legacy storage format to the new user-specific format.
    Why it matters: Existing users won't lose their consent preferences when upgrading to the new storage system.

Improvements​

  • Enhanced test coverage - Added comprehensive test suite for the migration functionality with 13 different scenarios covering edge cases and error handling.
    Why it matters: Ensures reliability and stability of the migration process across different user scenarios.

  • Robust error handling - Enhanced hashExtUsrData function to gracefully handle undefined values and improved storage operation error handling.
    Why it matters: Prevents runtime errors and ensures consistent behavior across different edge cases.

Deprecations​

  • None in this release.

Known Issues​

  • None at this time.

0.17.1​

January 20, 2026

Summary​

Enhanced developer documentation with comprehensive API reference and internal implementation details for better integration and debugging experience.

Improvements​

  • Comprehensive public API documentation: Added detailed method signatures, parameters, return types, and practical usage examples for all OsanoContext methods in the integration guide.
    Why it matters: Developers can now easily understand what each method does, how to use it correctly, and what to expect as return values.

  • Internal developer API reference: Extended README.dev.md with in-depth technical documentation including implementation details, performance optimizations, and debugging information.
    Why it matters: Internal developers and contributors can better understand the SDK's architecture, state management patterns, and troubleshooting approaches.

  • Enhanced method documentation: Documented all public methods (getConsent, clearConsent, getDeviceId, locale, setLocale, showBanner, showDrawer, isReady) with behavioral notes and best practices.
    Why it matters: Reduces integration confusion and provides clear guidance on proper usage patterns and timing.

Deprecations​

  • None in this release.

Known Issues​

  • None at this time.

0.17.0​

December 29, 2025

Summary​

Expands IAB TCF support by adding vendor disclosure handling end-to-end (selection, state, and TC string encoding), plus small spec-alignment updates for v2.3.

Improvements​

  • Spec alignment for disclosed-vendors segments: Updated internal mappings and options so the encoded TC string includes the vendor-disclosure segment.
    Why it matters: Ensures your consent signals meet current policy expectations across regions.

  • Active-vendor handling for cleaner disclosures: The SDK now filters out deprecated vendors and generates clean disclosure flags only for currently active vendors.
    Why it matters: Reduces noise and prevents stale vendor entries from appearing in consent/disclosure data.

  • Policy/version metadata refresh: Internal version and initialization options were aligned with the latest TCF policy vintage.
    Why it matters: Keeps your integration current with yearly policy/metadata updates without requiring app changes.

Learn more: IAB Europe TCF overview → https://iabeurope.eu/tcf-2-0/ · IAB Canada TCF → https://iabcanada.com/resources/transparency-consent-framework/

Deprecations​

  • None in this release.

Known Issues​

  • None at this time.

0.15.0​

December 04, 2025

Summary​

Run the SDK in Expo Dev Build and Expo Go without native modules and adopt React Native New Architecture (TurboModule) without changing your integration. Also includes a small dependency hardening and a minor deprecation.

New Features​

  • Expo Dev Build & Expo Go support - The SDK now falls back to in-memory storage (with device ID generation) when native modules aren’t available in Expo Go.
    Why it matters: You can prototype and test consent flows directly in Expo Go; production builds continue to use native storage. No code changes required.

  • React Native New Architecture (TurboModule) compatibility - Public interface exposed via TurboModule while remaining compatible with Legacy architecture.
    Why it matters: If your app switches to RN’s New Architecture, your Osano integration keeps working with no changes.

Improvements​

  • Dialog buttons & layout refinements - Adjusted components and layouts for clearer translations and modern RN behavior.
    Why it matters: More consistent user experience without API changes.

Deprecations​

  • None in this release.

Security​

  • Minor dependency hardening - Overrides applied to transitive JS packages to mitigate a resource-release issue.
    Why it matters: Improves supply-chain safety with no action required from integrators.

0.13.0​

July 31, 2025

Summary​

Adds Google Consent Mode v2 with a dedicated callback and automatic IAB TCF integration.

New Features​

  • Google Consent Mode v2 support.
  • onGoogleConsentUpdate callback prop to react to Google consent changes.
  • Automatic IAB TCF integration with Google Consent Mode.

0.12.0​

February 3, 2025

Summary​

Improves reliability and startup behavior with retries, readiness gating, and caching.

New Features​

  • Config caching with a 24-hour TTL.

Improvements​

  • Config fetch retries for robustness.
  • showBanner / showDrawer now wait until isReady is true.

0.11.0​

November 19, 2024

Summary​

Refines analytics copy and button behavior.

Improvements​

  • Updated dialog analytics translation (uses analytics wording correctly).
  • Updated Flavor 3 Accept button action.

0.10.0​

November 14, 2024

Summary​

Restores previously removed build artifacts for compliance.

Fixes​

  • Reverted USP & GPP build file removal.

0.9.0​

November 13, 2024

Summary​

Enables cross-device consent as a stable feature.

New Features​

  • Cross-device consent finalized.

0.8.0​

November 7, 2024

Summary​

Fixes consent payloads and adds external user data support for cross-device consent.

New Features​

  • extUsrData prop on the Osano component (for cross-device consent).

Fixes​

  • Corrected consent recording payload.

0.7.0​

October 16, 2024

Summary​

Prevents accidental usage of test endpoints in dev mode.

Fixes​

  • Development mode no longer routes to test API endpoints inadvertently.

0.6.0​

August 2, 2024

Summary​

Routine dependency refresh.

Improvements​

  • Dependencies updated.

0.5.0​

July 30, 2024

Summary​

IAB correctness and locale refinements.

Fixes​

  • Resolved edge case in IAB applying.

Improvements​

  • Locale updated.

0.4.0​

June 26, 2024

Summary​

Improves policy visibility and localization.

New Features​

  • Support for two policy links.

Improvements​

  • Locale updated.

0.3.0​

June 24, 2024

Summary​

Stability fixes for IAB actions and dialog behavior.

Fixes​

  • Fixed bug with IAB “Accept All” button.
  • Addressed dialog open issue.

0.2.0​

May 21, 2024

Summary​

Adds IAB TCF 2.2 support.

New Features​

  • IAB TCF 2.2 support.

0.1.0​

April 18, 2024

Summary​

Initial public release.

New Features​

  • First release of the SDK.