Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Blokada is displaying an ID string instead of the blocklist name in the activity log entries. #6

Closed
chrishub188 opened this issue Jun 2, 2024 · 4 comments
Assignees

Comments

@chrishub188
Copy link

chrishub188 commented Jun 2, 2024

Steps to reproduce

  1. Enable Blokada with multiple filter list, e.g. AdAway + 1Host Lite + OISD.
  2. Go to “Activity”
  3. Tab on any red entry that is blocked.

Expected behavior

Next to the red shield icon, the message appears, “This request has been blocked because it's present on the OISD blocklist.
(or whatever filter list is the blocking reason)

Actual behavior

Next to the red shield icon, the message appears, “This request has been blocked, because it's present on the
*03c351a2112a6633572fd2783f..

Additional information

The ID string changes based on the filter lists selected and the blocking reason. Occasionally, the name shows up, but mostly it's that long ID string. The behavior is the same for all entries. If the entry is on the custom block list, it is always displayed correctly.

Device information

  • iPhone 13 mini
  • Blokada 23.3.4 (Cloud)

IMG_5966
IMG_5972
IMG_5965

@chrishub188 chrishub188 changed the title Blokada is displaying an ID string instead of the Blocklist name in the Activity log. Blokada is displaying an ID string instead of the Blocklist name in the Activity log entries. Jun 2, 2024
@chrishub188 chrishub188 changed the title Blokada is displaying an ID string instead of the Blocklist name in the Activity log entries. Blokada is displaying an ID string instead of the blocklist name in the activity log entries. Jun 2, 2024
@balboah
Copy link

balboah commented Jun 10, 2024

Thank you for your detailed report, we will have a look at this!

@kar
Copy link

kar commented Jun 12, 2024

To be verified in the upcoming 24.x.x release.

@balboah
Copy link

balboah commented Aug 5, 2024

@chrishub188 is this issue still occurring for you in the latest version?

@chrishub188
Copy link
Author

The issue is fixed with the latest version.

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

No branches or pull requests

3 participants