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
We use this NPM package in a back-end Node.js service
We are not responsible for generating the GPP string, only processing it
We have no ability to force the end-user to use a specific version of the package when generating the GPP string
I'm working on updating our back-end service to use the latest version (3.1.5), but I'm finding unexpected results since 3.1.3.
My implementation is very basic:
// Setup...// CmpApi is not designed to work with NodeJs. mock the window objectglobal.window={};global.window.__gpp=()=>null;constcmpApi=newCmpApi(1,3);// Usage per request...cmpApi.setGppString(gppStr);constgppObj=cmpApi.getObject();
Here three randomly chosen GPP strings, and the results of getObject() for versions 3.1.1 through 3.1.5:
The user has clearly has the SaleOptOut/SharingOptOut/KnownChildSensitiveDataConsents set non-zero, but later package versions are returning a negative indicator for these keys. I can pass these strings into https://iabgpp.com and https://www.gppdecoder.com, and they return as expected.
Is there something I'm missing here? I found a lot of bumpy/breaking updates in the last few patch versions.
The text was updated successfully, but these errors were encountered:
Senario:
I'm working on updating our back-end service to use the latest version (3.1.5), but I'm finding unexpected results since 3.1.3.
My implementation is very basic:
Here three randomly chosen GPP strings, and the results of
getObject()
for versions 3.1.1 through 3.1.5:The user has clearly has the
SaleOptOut
/SharingOptOut
/KnownChildSensitiveDataConsents
set non-zero, but later package versions are returning a negative indicator for these keys. I can pass these strings into https://iabgpp.com and https://www.gppdecoder.com, and they return as expected.Is there something I'm missing here? I found a lot of bumpy/breaking updates in the last few patch versions.
The text was updated successfully, but these errors were encountered: