You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 16, 2024. It is now read-only.
Copy file name to clipboardExpand all lines: CHANGELOG.md
+4
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,7 @@
1
+
## 1.3.0 (Jun, 12, 2020)
2
+
* Store the `IABUSPrivacy_String` as spec'ed by the [CCPA IAB](https://github.com/InteractiveAdvertisingBureau/USPrivacy/blob/master/CCPA/USP%20API.md#in-app-support).
3
+
* Fixed an issue that'd prevent the consent message from showing again if the user dismissed it in the first place.
4
+
1
5
## 1.2.0 (April, 30, 2020)
2
6
* Added authenticated consent. For more details on how to use it check the README
Copy file name to clipboardExpand all lines: Example/Pods/Target Support Files/CCPAConsentViewController/ResourceBundle-CCPAConsentViewController-CCPAConsentViewController-Info.plist
Copy file name to clipboardExpand all lines: README.md
+52-51
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ We strongly recommend the use of [CocoaPods](https://cocoapods.org) in order to
8
8
In your `Podfile` add the following line to your app target:
9
9
10
10
```
11
-
pod 'CCPAConsentViewController', '1.1.3'
11
+
pod 'CCPAConsentViewController', '1.3.0'
12
12
```
13
13
### Carthage
14
14
We also support [Carthage](https://github.com/Carthage/Carthage). It requires a couple more steps to install so we dedicated a whole [wiki page](https://github.com/SourcePointUSA/CCPA_iOS_SDK/wiki/Carthage-SDK-integration-guide) for it.
@@ -30,19 +30,31 @@ It's pretty simple, here are 5 easy steps for you:
You need to give us a `authId`, that can be anything, user name, email, uuid, as long as you can uniquely identifies an user in your user base.
133
134
134
-
We'll check our database for a consent profile associated with that `authId`. If we find one, we'll bring it to the user's device and not show a consent message again (technically this will depend on the scenario setup in our dashboard). If we haven't found any consent profile for that `authId` we'll create one and associate with the current user.
135
+
We'll check our database for a consent profile associated with that `authId`. If we find one, we'll bring it to the user's device and not show a consent message again (technically this will depend on the scenario setup in our dashboard). If we haven't found any consent profile for that `authId` we'll create one and associate with the current user.
0 commit comments