Closed ym-corey closed 5 months ago
Confirmed that this is a bug related to encoding optimized ranges. The first 16 bits are allocated to a size value, which is correct in the first but wrong in the second. Fix incoming...
Fixed in 3.0.10. And I was wrong in my last comment. The second one was actually correct.
I noticed while including some tests in my code, that sometimes under conditions I haven't worked out yet, the GppModel's TcfEuV2 can decode to a different value... Not sure if this is the only case that something like this happens.
There is a difference between the
fromObjectModel
anddecodedModel
, being that theheader
section isn't present in the former. However, my understanding is that when the other sections of the GPP string change, the section for TcfEuV2, delimited by ~, should remain unchanged.Results:
The first and second printout should be the same, but are not. The third printout should include the first value, after the delimiter, but it doesn't -- it is the 2nd value after the delimiter.
I have noticed that the values for
TcfEuV2Field.SPECIAL_FEATURE_OPTINS
andTcfEuV2Field.PURPOSE_LEGITIMATE_INTERESTS
are empty infromObjectModel
and are non-empty (contain arrays filled withfalse
) indecodedModel
, but even when setting the values to the same thing I still see different consent strings.e.g.,