Skip to content

Releases: SourcePointUSA/ios-cmp-app

5.3.2

23 Nov 15:38
Compare
Choose a tag to compare
  • Fixed a regression with the sharing consent with the webview feature

5.3.1

23 Nov 10:05
Compare
Choose a tag to compare

5.3.1 (Nov, 23, 2020)

  • Fixed an issue that would prevent the consentLanguage field from the consent string to always be set to EN. #260
  • Added a feature to ease sharing consent between native and webviews. Check how to use it in this section of the README. #263
  • Fixed an issue that prevented the property .userConsents from the GDPRConsentViewController to be outdated after calling the .customConsentTo method. #264
  • Updated the README and the AuthExample app.

5.3.0

19 Oct 14:58
Compare
Choose a tag to compare
  • Added support to Swift Package Manager(SPM)

5.2.10

15 Oct 13:14
Compare
Choose a tag to compare
  • improve error handling on MessageWebView #247

5.2.9

13 Oct 16:04
Compare
Choose a tag to compare
  • Fixed compatibility with Xcode 12.x

5.2.8

21 Aug 13:43
Compare
Choose a tag to compare
  • improved the error handling code of our WebMessageViewController. #229 (thank you @ivanlisovyi)

5.2.6

11 Aug 12:00
Compare
Choose a tag to compare
  • fixed an issue that'd, in some cases, prevent authenticated consent from being stored #224
  • disabled "back and forward" gestures in the WebView, to prevent users from skipping the consent message when no dismiss button is present. #221
  • we are now getting the privacy manager id from the consent message when the user taps on Show PM instead of using the one provided to the SDK via constructor. #201
  • fixed an issue that'd prevent GDPRMessageJson from having all its fields encoded #218 (thank you @ivanlisovyi)
  • considerably increase UI test coverage for both Native and Web messages.

5.2.5

03 Jul 09:04
Compare
Choose a tag to compare
  • fixed an issue that'd prevent the consent message from showing up on iOS 10

5.2.4

25 Jun 14:56
Compare
Choose a tag to compare
  • fixed an issue preventing the vendorGrants from being filled in when calling customConsentTo.
  • cache the user's consent in the UserDefaults
  • we now make sure the onConsentReady is always called (except when returning from the PM to the consent message).
  • increase test and code coverage

5.2.3

09 Jun 10:17
8a14163
Compare
Choose a tag to compare

Fixed an issue that'd prevent the user from interacting with the app when the PMId passed to the SDK was wrong. We now encapsulate that in a WebViewError and call the onError callback on the ConsentDelegate.