Skip to content
This repository has been archived by the owner on Oct 27, 2022. It is now read-only.

[BUG] Wrong information for check on consent telemetry #129

Open
adrianriobo opened this issue Aug 19, 2021 · 4 comments
Open

[BUG] Wrong information for check on consent telemetry #129

adrianriobo opened this issue Aug 19, 2021 · 4 comments

Comments

@adrianriobo
Copy link
Contributor

Testing on pre-release 1.31.2 on qe environments

In case of missing crc.json file the tray visual element to represent the consent telemetry appears as checked. Even if telemetry is not sent the visual information can be confusing.

@adrianriobo adrianriobo changed the title [BUG] Wrong information for check for consent telemetry as checked [BUG] Wrong information for check on consent telemetry Aug 19, 2021
@gbraad
Copy link
Contributor

gbraad commented Aug 19, 2021

In case of missing crc.json file

interesting observation, as we only deal with the information we get from the backend. So this might mean that the information we get might indicate something else?

@gbraad
Copy link
Contributor

gbraad commented Sep 27, 2021

It seems ConsentTelemetry has an empty value "" which might cause this behaviour.

Seems the checkbox for consent uses a very different logic as was chosen to be a string instead of a boolean.

@gbraad
Copy link
Contributor

gbraad commented Sep 27, 2021

Seems the checkbox for consent uses a very different logic as was chosen to be a string instead of a boolean.

Should be an onboarding question?

@gbraad
Copy link
Contributor

gbraad commented Sep 28, 2021

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants