Repository navigation
Document the IAB GPP UserDefaults keys the SDK now reads - #88
Merged
Merged
Conversation
#86 switched the gpp fallback to IABGPP_HDR_GppString and added an IABGPP_GppSID fallback for gppSid, so the consent table and the "gppSid has no fallback" paragraph in both guides were out of date. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
juanli16
approved these changes
Nov 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
#86 changed where the SDK reads GPP consent from:
gppnow falls back toIABGPP_HDR_GppString(with the oldIABGPP_2_TCStringas a second fallback), andgppSidnow falls back toIABGPP_GppSID. The consent section added in #79 still described the old behavior in both guides.Notes:
IABGPP_2_TCString. Best merged with (or after) the release that includes Read GPP consent from the IAB's UserDefaults keys #86.