search

cookie-information / android-release

0 stars 3 forks source link

Custom consents are not stored correctly #7

Closed LasseMortensen closed 1 year ago

LasseMortensen commented 1 year ago

Consent with setting types are not stored correctly.

Version 1.0.4

Steps to reproduce

Have multiple consents with consent type as Setting

  1. Open the SDK ui by calling displayConsents
  2. Choose accept all
  3. Close the app
  4. Start the app again
  5. Open the SDK ui again by calling displayConsents

Actual result Only native type consents (TypeNecessary, TypeMarketing, etc.) are selected and no custom types are selected (Setting)

Expected result All consents are shown as selected

Issue

When storing purposes locally you usetype.name as identifier in storeConsentChoices . The type.name value seems to always be "custom" although we would like it to be the same as shortText. This result in all custom consents being overridden by the next custom consent when being saved.

image

LasseMortensen commented 1 year ago

Confirmed working in version 1.0.5, thanks