Extension keeps asking for login

[Mornon]

After Feedly Notifier has come back to Chrome, every time I click on the notification it asks me to login, despite the fact that I already did and I'm marked as login in the extension's page. I also tried uninstalling and reinstalling it, same issue.

To Reproduce Steps to reproduce the behavior:

1. Pin the icon
2. Set the extension to open Feedly site when clicked
3. Click on the icon (if it doesn't require login, wait to have new feeds, and a bit of time)

Expected behavior The site should open.

Screenshots My current options, if needed:

Desktop (please complete the following information):

• OS: Windows 10 Pro 10.0.19045 Build 19045
• Browser: Chrome
• Version 139.0.7258.155

[TomskDiver]

Same issue. Often asks login. Take this window:

After click Sign in with Google, take this:

After that may click on Feedly Notify icon and it open Feedly.

[viruseg]

It also requires authorization after each restart of Chrome.

[Mornon]

I also tried uninstalling and reinstalling it, same issue.

[olsh]

I tried to fix the issue in the new version (3.0.1). Let me know if it's fixed.

[Mornon]

Should I wait for it on the store, or install it from somewhere else?

By the way, an easy temporary fix is just click again on the icon, Feedly will open without asking for login.

[TomskDiver]

Version 3.0.1

@olsh The fix didn't help.

[olsh]

Could you check if the background worker has any issues? Go to chrome://extensions/, enable Developer Mode, click on the Feedly Notifier service worker link, and check the console for errors.

[Mornon]

The console comes up empty, "No issue" written on the left of the gear icon.

[Mornon]

Should I check it at any moment, or before/after/during clicking on the icon an getting the login request?

[olsh]

@Mornon try to enable the Collect errors options on the page chrome://extensions/?id=egikgfbhipinieabdmcpigejkaomgjgb

[viruseg]

I think I've figured out what's causing the repeated authorization request. Domain olsh.me it is blocked in the Russian Federation. When switching to feedly.com redirection to the domain is taking place olsh.github.io , which redirects to olsh.me And since olsh.me blocked, then the redirect gets stuck. But for some reason, when clicking on the Feedly Notifier icon again, feedly.com it opens immediately. If you try to log in after a few hours feedly.com using the Feedly Notifier icon, the transition will be blocked again. There are no errors in the Feedly Notifier console, the problem does not concern the extension code.

[olsh]

@viruseg Well, the domain is not actually blocked. It uses the ECH feature, which RKN doesn’t like.

You can temporarily disable ECH just for testing, but I strongly recommend not keeping it disabled:

chrome --disable-features=EncryptedClientHello

[Mornon]

@Mornon try to enable the Collect errors options on the page chrome://extensions/?id=egikgfbhipinieabdmcpigejkaomgjgb

Should I go to chrome://extensions/, enable Developer Mode, click on the Feedly Notifier service worker link, go to chrome://extensions/?id=egikgfbhipinieabdmcpigejkaomgjgb and check the console for errors? If so, then no error.

[viruseg]

I added the --disable-features=EncryptedClientHello key, but the problem persisted. Domain olsh.me no longer blocked with this key. But clicking on the Feedly Notifier icon still redirects to reauthorization. And after the second click it opens the website. feedly.com . In developer mode, I don't see any errors in the extension.

[kimi-0]

On the extension’s details page, there are times when the Service Worker shows as (Inactive), and if you click the extension icon at that moment, it redirects to the login page. However, if the console is open, the Service Worker does not stop, so this issue does not occur. In the current version of Chrome, the Service Worker is terminated if it takes no action for 30 seconds. This behavior is being discussed in the Chromium Issue Tracker ( https://issues.chromium.org/issues/40733525 ).

[olsh]

@kimi-0 I'm aware of the behavior. When the state changes from inactive to active, the extension loads its data from Chrome storage. You can check the state in the Service Worker DevTools under Application > Extension Storage > Sync or Local (depending on whether you enabled option sync for the extension).

This login issue does not affect all users, and I haven’t been able to reproduce it myself, even though I use the extension every day. Could you please check if the settings are saved to the storage?

[kimi-0]

All the data appears to be saved correctly. I also deleted the Local/Sync data and reconfigured it, but the issue still reoccurs.

When inspecting the Service Worker via chrome://serviceworker-internals/, the problem reproduces immediately.

[olsh]

I tried stopping/unregistering the extension via chrome://serviceworker-internals/, but no luck—I still can’t reproduce the issue.

[TomskDiver]

Make debug version of extension (wrap logging for listeners and functions in core.js, not background.js). I click 11:07:14 icon and get login page:

[
    "[2025-09-30T10:37:31.138Z] Сработал listener tabs.onRemoved(759800682, {\"isWindowClosing\":false,\"windowId\":759800427})",
    "[2025-09-30T10:37:31.244Z] Вызов функции appGlobal.startSchedule(10, false)",
    "[2025-09-30T10:37:33.316Z] Сработал listener tabs.onRemoved(759800438, {\"isWindowClosing\":false,\"windowId\":759800427})",
    "[2025-09-30T10:43:59.541Z] Вызов функции appGlobal.ensureOptionsLoaded()",
    "[2025-09-30T10:43:59.547Z] Вызов функции appGlobal.updateCounter()",
    "[2025-09-30T10:43:59.549Z] Вызов функции appGlobal.startSchedule(10, false)",
    "[2025-09-30T10:44:00.011Z] Вызов функции appGlobal.setBadgeCounter(63)",
    "[2025-09-30T10:53:59.557Z] Вызов функции appGlobal.ensureOptionsLoaded()",
    "[2025-09-30T10:53:59.561Z] Вызов функции appGlobal.initialize(false)",
    "[2025-09-30T10:53:59.562Z] Вызов функции appGlobal.updateCounter()",
    "[2025-09-30T10:53:59.562Z] Вызов функции appGlobal.apiRequestWrapper(\"markers/counts\", {})",
    "[2025-09-30T10:54:00.314Z] Вызов функции appGlobal.setBadgeCounter(64)",
    "[2025-09-30T11:03:59.554Z] Вызов функции appGlobal.ensureOptionsLoaded()",
    "[2025-09-30T11:03:59.558Z] Вызов функции appGlobal.updateCounter()",
    "[2025-09-30T11:03:59.558Z] Вызов функции appGlobal.apiRequestWrapper(\"markers/counts\", {})",
    "[2025-09-30T11:03:59.994Z] Вызов функции appGlobal.setBadgeCounter(66)",
    "[2025-09-30T11:07:14.656Z] Вызов функции appGlobal.getAccessToken()",
    "[2025-09-30T11:07:14.693Z] Вызов функции appGlobal.initialize(false)",
    "[2025-09-30T11:07:14.699Z] Вызов функции appGlobal.startSchedule(10, false)",
    "[2025-09-30T11:07:21.893Z] Сработал listener tabs.onRemoved(759800687, {\"isWindowClosing\":false,\"windowId\":759800427})"
]

Need debug changes for isLoggedIn property?

[mwhaley99]

I am having the same issue.

[erseco]

Still happening

[olsh]

I managed to reproduce the bug. It should be fixed in the 3.0.3 version, which is on review now.

[olsh]

The fixed version was published. Please check if the issue was resolved.

[kimi-0]

I've been using it for a while and it seems to be working great. Thank you.

[viruseg]

Since the update to version 3.0.3, everything has been working perfectly. It looks like the issue has been resolved.

[Mornon]

I still have to use it a bit, but I can confirm until now it doesn't seem to have the bug anymore, thanks.