Mobile & OTT/CTV App Consent - June 26, 2026 - 202606.2.0

Fixed Android

  • Resolved an issue that sent blank consent receipts for purposes not configured by the end user. The SDK now only submits receipts for purposes the user changed.

Fixed iOS

  • The NSPrivacyAccessedAPITypeDeclaredAgeRange key has been removed from the SDK to prevent apps from being rejected from Apple's App Store.

  • Resolved an issue that caused some React Native SDK builds to fail after calling deprecated methods.

  • Resolved an issue that prevented the SDK from logging consent preferences made while the user's device was offline.

Fixed HTML5

  • Resolved an issue that displayed the Store and/or access consent purpose on the preference center after the purpose had been disabled in the admin interface.

New Public Preview Features

Link Age Ranges to Purposes

Link age ranges to categories and purposes for enhanced compliance with Age Gate requirements. This enhancement allows you to configure your SDK to hide specific categories or purposes to prevent users from consenting to those specified categories or purposes.

This feature is available for the following platforms:

  • Android

  • iOS

For more information, see Configuring Age Gate Prompts for Mobile Apps,

Enhancements to Consent Management Platform APIs

The following enhancements have been made to the Consent Management Platform (CMP) APIs: 

  • Updated the errors object of CMP API responses to include ERROR_CODE_EMPTY_CONSENT as a response for the code parameter and At least one purpose consent is required as a response for the message parameter. This error is returned by the Log Consent API when logging Universal Consent preferences with OT-Explicit-Consent: true and an empty payload. This enhancement adds error handling to avoid generating empty receipts and ensure that at least one consent is captured.

Age Based Consent is now supported for the CMP APIs. The following enhancements allow you to capture and manage age range information as part of the consent flow, enabling age-based experiences within your applications.

  • Updated the Log Consent API to include AGEGATE_RANGE as a value for the interactionType request parameter and to include the new ageGate request parameter. When interactionType is set to AGEGATE_RANGE, the ageGate parameter is required to configure the necessary age range for age-based consent capture.

  • Updated the Get Banner Data API to include the linkedCategories parameter to return the list of consent categories linked to age groups within the ageGate parameter of the prompts object of the response.

  • Updated CMP API Responses to include the new OT_AgeGate parameter within the storageKeys object of the response.

  • Updated the errors object of CMP API responses to include ERROR_CODE_INVALID_AGE_RANGE as a response for the code parameter and The upper bound of the age range must be greater than lower bound as a response for the message parameter.

Existing Public Preview Features

Consent Management Platform APIs

The following APIs are now available for use with retrieving interface attributes needed to display the Banner and Preference Center, retrieving a list of active IAB and Google Vendors to display on the Preference Center, and logging consent when an end user interacts with a Banner or Preference Center. These APIs enable you to easily access data for Banner and Preference Center implementations, disclose vendor information to end users, and capture end user consent.

Roku Support for Unified Consent Profile for Known Users

Leverage the new Unified Consent Profile for Known Users functionality to connect data subjects' CMP preferences with Universal Consent & Preference Management profiles by enabling the Create data subject profiles for known users setting on the Geolocation Rules tab. You can also easily trigger integration workflows to send CMP preferences to downstream systems, and efficiently manage your preferences in a unique Preference Center, centralizing all of them in one single profile.

This enhancement provides a comprehensive view of data subjects empowering you with more control over the data captured across both modules, resulting in a more streamlined and tailored user experience.

For more information, see Connecting CMP preferences with Universal Consent & Preference Management Profiles.

Configure Button Layout for the Banner

Configure the positioning of buttons on your mobile and CTV banners within the Button Sets section of the Template Details screen. This enhancement allows you to specify the positioning of buttons on your banners for a more customized experience.

  • iOS

  • Android

For more information, see Customizing the Mobile App Consent Banner Template and Customizing the Mobile App Consent Preference Center Template.

Enhanced Branding Settings for Mobile and CTV SDKs

Configure detailed branding settings for your mobile SDKs on the Branding tab of the Mobile App Details and CTV App Details screen, respectively. This enhancement enables you to configure more specific branding settings for each of your mobile and CTV applications.

For more information, see Configuring Mobile and CTV App Branding.

Validation for Cross-Device Consent Receipts

Enable the Require Authentication for known users setting when leveraging Cross-Device Consent to require validation on your consent receipts. This enhancement allows you to more reliably collect consent from known users.

For more information, see Configuring Geolocation Rules.

Note:

This enhancement is only available to users with the Consent Rate Optimization (CRO) add-on package. Contact OneTrust Support or your account representative to enable this functionality.

To learn more, see Maximize Opt-Ins with Consent Rate Optimization.

Authenticated Consent for New and Existing Users

Transfer consent from local storage to new and existing data subject IDs (DSIDs) for user profiles when leveraging Cross-Device Consent. This enhancement allows you to apply previously captured consent to user profiles to streamline consent collection.

This feature is available for the following platforms:

  • iOS

  • Android

  • Apple TV

  • Android TV

Enable Global Privacy Protocol on TCF 2.2 Templates

Enable the Global Privacy Protocol setting on TCF 2.2 templates. This setting allows you to enable the IAB Tech Lab - Global Privacy Protocol (GPP) and populate the IAB TCF EU section of the GPP string.

This feature is available for the following platforms:

  • Android

  • Android TV

  • Apple TV

  • HTML5

  • iOS

  • Roku

  • Unity

  • Xamarin

For more information, see Configuring the Global Privacy Protocol Settings.

New Reject All Button Configuration

Enable the updated Reject All button configuration on the Preference Center template. This new configuration ensures that legitimate interest is not impacted for customers using Google Ads.

For more information, see Customizing the Mobile App Consent Preference Center Template.

Things to Know

You can now select a version of the iOS Privacy Manifest after correcting mismatches to amend your corrections and review historical versions of the privacy manifest on theScan resultstab of theMobile app detailsscreen. Additionally, you can export your selected version of the manifest file by selecting the Export icon.

For more information, see Viewing and Categorizing Mobile App Consent Scan Results.

About Known Defects

 

Issues that may impact our customers are documented in our Known Defects Database located here with approved workarounds and targeted releases for resolving the issue.