Google UMP generating invalid TCString

[Gonçalo Silva (AppGeneration)]

Hi,

Since 8th November, GDPR users of my app have been receiving the updated consent form for TCF v2.2 (policy version 4), instead of the older TCF v2.0 form (policy version 2).

The old form has been working without issues.

The new form is generating an invalid TCString that does not respect the TCF v2.2 specification, and is causing issues in my application code.

If I try to decode the generated string using the IAB TCF decoder (https://iabtcf.com/#/decode), it does not produce a valid output.

This is the string that I get after selecting "Consent All" on the TCF v2.2 form:

DP1BnkAP1BnkAEsACCENAaEgAAAAAEPgAB6YAAAQaQD2F2K2kKFkPCuQWYoQBCijaEAhQBAAAkCBIAAgAUgQAgFIIAgABFAAEAAAAAAQEgCQAAQABAAAIACgAAAAAAIAAAAAAAQQAAAAAIAAACAAAAEAQAAAAAQAAAAIAABEhCAAQQAMAAAAAAASAAAAAAAAAAABAAAAAAAAAAAAAAQAAAAAgAA.YAAADmAAAAA

The first "D" character would correspond to "TCF Core Version 3", which doesn't exist according to their official documentation. I reached out to the IAB TCF team in Github, and they confirmed the generated TCString is invalid.

https://github.com/InteractiveAdvertisingBureau/iabtcf-es/issues/429

According to your team, is this information correct?

When can we expect a fix for this issue?

Best regards

[Mobile Ads SDK Forum Advisor]

Hi,

I see that you have already raised this concern on another thread with the subject 'UMP SDK for TCF v2.2 is generating invalid TCString', and we have already responded to this issue. To avoid multiple threads on the same issue, please take a look at that thread and continue the discussion on the same for further updates on the issue.

Please reach out to us, if you need any further assistance.
 

This message is in relation to case "ref:!00D1U01174p.!5004Q02qBs8e:ref"

Thanks,
 

Mobile Ads SDK Team