Skip to main content

Changelog

3.6.5​

February 25, 2026

Summary​

Centralizes all translation keys, improves translation reliability for mobile apps. The SDK now uses mobile-specific translations when available, with automatic fallback to web keys.

Improvements​

  • Centralized translation keys — All translation keys are now defined with a prefix for mobile-specific strings.
    Why it matters: Makes it easier to update, audit, and maintain localizations across your app.

  • Smarter translation lookup — The SDK checks for mobile-specific translations first, then falls back to web keys in both customer and global translation maps.
    Why it matters: Ensures users always see the most relevant, up-to-date text with less developer effort.

  • UI and IAB translation consistency — All UI and IAB-related translation lookups now use the new centralized keys. Policy links and consent screens are easier to localize and maintain.
    Why it matters: Reduces the risk of missing or inconsistent translations, and simplifies localization updates.

Action Required​

To use mobile custom translations, add or update your strings in your web configuration (Osano dashboard).

Known Issues​

  • None at this time.

3.6.4​

February 3, 2026

Summary​

Architectural improvements to ConsentManager initialization, improved user context switching performance, and fixes for drawer toggle synchronization issues.

Bug Fixes​

  • Drawer toggle synchronization: Fixed issue where consent category toggles in the preferences drawer would not reflect the correct user's consent state immediately after user switching.
    Why it matters: Users now see accurate toggle states that match their stored consent preferences, eliminating confusion about their actual consent status.

New Features​

  • Smart ConsentManager re-initialization: Added controlled re-initialization logic that only triggers when customerId or configId or extUsrData changes on an already initialized instance.
    Why it matters: Improves user switching performance while ensuring fresh consent data is properly loaded for each user or configuration context.

Improvements​

  • Optimized initialization flow: Eliminated redundant network requests during ConsentManager property setup.
    Why it matters: Faster SDK initialization and reduced network overhead, especially beneficial for apps with frequent user switching.

  • Improved user context isolation: Enhanced user context switching to ensure proper consent data isolation between different users.
    Why it matters: Better data privacy and more reliable cross-user consent management in multi-user scenarios.

Known Issues​

  • Race condition during user switching: There's a brief moment during extUsrData updates where async consent lookup may still be in progress.
  • Recommendation: Avoid calling showDialogViewController() immediately after changing extUsrData.

3.6.3​

January 26, 2026

Summary​

Major improvements to user consent isolation, automatic migration system, and enhanced remote consent handling for cross-device scenarios.

Bug Fixes​

  • Cross-user consent data leakage: Fixed critical issue where consent data was persisting across different user login/logout sessions.
    Why it matters: Users now see only their own consent preferences, ensuring proper privacy isolation between different user accounts when using cross-device consent functionality.

New Features​

  • Automatic consent migration: Legacy consent data is automatically migrated to user-scoped storage on SDK upgrade.
    Why it matters: Existing users won't lose their consent preferences when you update to this version - migration happens seamlessly in the background.

  • Enhanced cross-device consent handling: When external user identifiers are provided, the SDK now always stores remote consent from your backend.
    Why it matters: Ensures cross-device consent synchronization works reliably and prioritizes server-side consent state over local storage.

Improvements​

  • User-scoped consent storage: Consent data is now isolated per user context using secure identifiers.
    Why it matters: Prevents consent data leakage between different users of the same app instance, critical for multi-user applications.

  • Code quality improvements: Refactored internal architecture to eliminate duplicate code and improve maintainability.
    Why it matters: More reliable SDK behavior and easier troubleshooting for your development team.

Migration Guide​

No code changes required - the SDK handles migration automatically. However, note these behavior changes:

  • Cross-device consent: If you use extUsrData for cross-device consent, the SDK now prioritizes remote consent over local consent in all cases.
  • User isolation: Consent data is now properly isolated per user session. Call clearConsent() or clearAllUsersConsent() if you need to reset consent data during testing.

Known Issues​

  • None at this time.

3.6.2​

December 22, 2025

Summary​

Improves consent correctness and transparency under the latest IAB TCF policy and adds platform attribution to consent records.

New Features​

  • Platform attribution in consent records (iOS): The SDK now distinguishes between production apps and official samples when tagging the originating platform in consent records.
    Why it matters: Enables cleaner reporting and troubleshooting across environments without requiring integrator code changes.

Improvements​

  • IAB TCF policy alignment: Default behavior aligns with the most recent IAB TCF policy expectations.
    Why it matters: Keeps your consent signaling and downstream ad-tech interoperability compliant with current standards.

Note: Visit IAB Tech Lab - Consent string and vendor list formats v2 to get more information about vendor disclosure

  • Accurate vendor disclosure after consent changes: Vendor disclosure is automatically kept in sync whenever a user updates their consent choices.
    Why it matters: Ensures audit-ready transparency and consistent reporting for privacy reviews.

Known Issues​

  • None at this time.

3.6.0​

July 31, 2025

Summary​

Adds an optional debug logging toggle for troubleshooting and refreshes localizations across supported languages.

New Features​

  • Debug logging toggle: You can enable verbose SDK logging during development/testing.
    Why it matters: Speeds up diagnostics and support interactions without shipping noisy logs to production.

Improvements​

  • Localization refresh: Updated translations across supported languages.
    Why it matters: More consistent and accurate UI copy for end-users.

3.5.0​

March 21, 2025

Summary​

Introduces integration with Apple’s App Tracking Transparency (ATT).

New Features​

  • ATT framework integration: The SDK now interoperates with ATT to respect system-level tracking authorization.
    Why it matters: Aligns consent UX with platform requirements; improves user trust and app store compliance.

Learn more: Apple ATT → https://developer.apple.com/documentation/apptrackingtransparency

3.4.0​

November 12, 2024

Summary​

Enables cross-device consent and adopts Apple’s privacy manifest.

New Features​

  • Cross-device consent: Consent can be recognized across sessions/devices when an external, privacy-safe identifier is provided.
    Why it matters: Reduces repeat prompts and gives a consistent consent state for multi-device users.

  • Privacy manifest (PrivacyInfo.xcprivacy): The SDK declares data use in Apple’s privacy manifest format.
    Why it matters: Improves transparency and helps meet App Store privacy requirements.

Learn more: Apple Privacy Manifests → https://developer.apple.com/documentation/bundleresources/privacy_manifest_files

3.3.2​

September 16, 2024

Summary​

Fixes a platform-specific issue on iOS 16.0–16.3 when using domain-scoped consent behavior.

Fixes​

  • Domain-scoped consent on iOS 16.0–16.3: Corrected behavior that could impact consent resolution on those OS versions.
    Why it matters: Ensures reliable consent evaluation on older iOS 16 builds.

3.3.1​

August 29, 2024

Summary​

Clarifies IAB banner copy to include required special feature language.

Improvements​

  • IAB banner copy: Updated message to cover special-feature disclosures.
    Why it matters: Better compliance and user clarity under IAB guidance.

3.3.0​

June 26, 2024

Summary​

Adds Google Consent Mode support, improves initialization ergonomics, enhances IAB stability, introduces a second policy link, resolves an iPad crash, and streamlines translation fetching.

New Features​

  • Google Consent Mode support Why it matters: Lets you propagate consent signals to Google tags for measurement and ads use-cases.

Learn more: Google Consent Mode → https://developers.google.com/tag-platform/security/concepts/consent-mode

  • Initialization completion handlers
    Why it matters: Easier to sequence app logic after the SDK is fully ready.

  • Second policy link
    Why it matters: Surface multiple policy resources (e.g., Privacy Policy + Do Not Sell/Share) in the UX.

Fixes​

  • IAB stability fixes
    Why it matters: More reliable consent strings and vendor/feature handling.
  • iPad preferences drawer crash
    Why it matters: Prevents a UX-blocking crash on larger devices.

Improvements​

  • Translation fetching
    Why it matters: More consistent and up-to-date localized copy.

3.2.0​

March 26, 2024

Summary​

Corrects analytics toggle behavior and adjusts Accept All handling for a specific banner flavor.

Fixes​

  • Analytics toggle state
    Why it matters: Ensures the analytics category reflects user intent.

Improvements​

  • Accept All behavior (specific banner flavor)
    Why it matters: Aligns the one-tap action with expected consent outcomes.

3.1.1​

March 19, 2024

Summary​

Fixes a regression in GDPR applicability checks.

Fixes​

  • GDPR scope detection: Accurately determines when GDPR rules should apply before enforcing consent.

3.1.0​

January 9, 2024

Summary​

Finalizes support for IAB TCF 2.2.

New Features​

  • IAB TCF 2.2: Aligns consent signaling and vendor/feature handling with the IAB’s latest framework updates.

Learn more: IAB Europe TCF → https://iabeurope.eu/tcf-2-0/