On migrating from 202209.2.0.0 to a newer version, we rant into a problem where after calling saveConsent(..bannerAllowAll) we then called OTPublishersHeadlessSDK.shared.getOTConsentJSForWebView() and noticed that none of our consent categories were set.
On closer inspection, the method signature changed, to include a completion callback, which I guess made the call essentially an async one. We were able to alter our code to trigger getOTConsentJSForWebView in the callback.
The documentation at https://developer.onetrust.com/onetrust/docs/api-reference-ios-tvos#banner-allow-all doesn't refer to the callback parameter, nor could I find release notes that highlighted the change.
On migrating from 202209.2.0.0 to a newer version, we rant into a problem where after calling saveConsent(..bannerAllowAll) we then called OTPublishersHeadlessSDK.shared.getOTConsentJSForWebView() and noticed that none of our consent categories were set. On closer inspection, the method signature changed, to include a completion callback, which I guess made the call essentially an async one. We were able to alter our code to trigger getOTConsentJSForWebView in the callback. The documentation at https://developer.onetrust.com/onetrust/docs/api-reference-ios-tvos#banner-allow-all doesn't refer to the callback parameter, nor could I find release notes that highlighted the change.