Closed LasseMortensen closed 1 year ago
It seems to be an issue where the token is null as it have not yet been saved in preferences. It looks like it will only be saved in the view model but we will not call displayConsents
if the user accepts all or necessary consents in our dialog
Hello! Yes, you are right. A valid token for your consent has not been requested. I will be adding a verification for a valid token prior to posting the consent.
Version 1.0.4 seems to fix the issue, thanks ✅
Hi
Issue postConsent returns 401 invalid_token Version: 0.2.7
Background I'm trying to implement a dialog where the user can choose to accept to all consent, all required or custom (opens your UI). The first two options require
postConsent
to be called but it returns 401 invalid_token. HoweverfetchConsentSolution
,shouldDisplayConsents
anddisplayConsents
works fine.Implementation Post method:
createConsent method:
Error log