Feedly Notifier not refreshing the list correctly anymore

[RejZoRSheep]

Describe the bug
It's not updating/refreshing the list since recently. I mark entry as "Mark as read" and when I open the Feedly Notifier popup again, the same entries are there again that were marked as "Mark as read". I've tried logging into Feedly again, but it's still not refreshing.

To Reproduce
Steps to reproduce the behavior:

1. Open Feedly Notifier extension popup
2. Mark any entry on the feeds list as "Mark as read"
3. Close extension popup
4. Re-open Feedly Notifier and the "Mark as read" entries will still be there

Expected behavior
Entries marked as read should disappear from the list when marked.

Screenshots
Not applicable

Desktop (please complete the following information):

• OS: Windows 11 24H2
• Firefox
• Version 132.0.2

[atos93]

Same bug also for me on
Desktop:

OS: Windows 11 23H2
Chrome
Version 131.0.6778.70

I've marked some articles as read on the Feedly website, but the add-on isn't refreshing.
I also tried logging off from the application, but I can’t log back in; I’m redirected to this page:
https://olsh.me/Feedly-Notifier/?error=server_error&error_description=Internal%20error&state=1731486268143

EDIT:
After some time, even the feeds in Feedly revert to their initial state, even if they’ve been marked as read. At this point, I think it’s a general issue with Feedly and not related to the add-on.

[Thorketil]

Same bug also for me on
Desktop:

OS: Fedora Linux 40 (Workstation Edition)
Firefox
Version 132.0 (64 bits)

Tried to uninstall/reinstall the extension too, with no success, and I agree:
the problem seems to be on the Feedly side even though it happened concomitantly with the add-on update.

[vargn]

Desktop:

OS: Arch Linux
Brave Version 1.71.123 Chromium: 130.0.6723.116 (Official Build) (64-bit)

Same here, tried logging out and in again. But it rejects my login and redirects me to a "Server error" page: https://olsh.me/Feedly-Notifier/?error=server_error&error_description=Internal%20error&state

Related to #281 most likely

This really puts a dent in my routine workflow, and I don't like it lol

[vargn]

Confirmed working again, thanks!