Skip to content

MSPA fields not populating correctly when parsing USNAT consent string #18

@efixler

Description

@efixler

I'm generating GPP consents string, with a USNAT section, using https://iabgpp.com.

Here is an [example](see: https://iabgpp.com/#DBABLA~BVQVAAAAAABY.QA) string that reflects the settings that are required for the application I'm working on. The actual string is DBABLA~BVQVAAAAAABY.QA.

This string is decoded as expected with the iabgpp tool (and with other online tools as well), but when parsing this string with go-gpp the MspaXxx fields are not populated, they are all 0.

Here is a gist that demonstrates the issue.

Appreciate 👀 and assistance. Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions