Migrate from TCF v1 to TCF v2
Consent signals for TCF v1 are not compatible with TCF v2 due to IAB policies. Users with an existing TCF v1 answer will be exposed to the TCF v2 consent notice as if they were new users.
Update Ogury SDK version in your Cocoapods
Podfilefile or download the last
OguryChoiceManager.framework. Use the latest version of the Ogury SDK.
First thing after updating the version that you should done is initialization of the Choice Manager and ask for the consent. You should follow usual steps to be sure that
setupis called first and after that
Each method call should be changed to use new approach, this is the pattern:
OguryChoiceManager.shared().tcfV2.methodName.Make sure that you replaced all method calls in your project and do not call methods for TCFV1.
For example, following code:
[[[OguryChoiceManager sharedManager] tcfV1] getIabString];
should be replaced with following code:
[[[OguryChoiceManager sharedManager] tcfV2] getIabString];