Kagi Extension API Key Not Persistent in Firefox ESR on Kali Linux

Thanks for reporting this @Maxpl01t . Can you confirm if this is the same issue as reported in https://github.com/kagisearch/browser_extensions/issues/27#issuecomment-1735185298 ? Basically, do you have the option to delete browser history on quit?

Thanks for clarifying @Maxpl01t . It might not be different, it just depends on how the extension was initially setup, but if you setup a manual session token in it, does that get stored/saved, or is it also lost? (if you don't set it up manually, it should never be lost because it'll be read from kagi.com assuming you're logged in)

Thanks for looking into it. I don't know what might be the issue, then, and I can't replicate it. Can you see any errors for the extension?

@KGuser can you please try, in the extension's permissions/settings, disabling the "Run in Private Windows" toggle, saving the token, then enabling it again?

Thanks for the extra details @KGuser , the errors you mention in the second post don't seem relevant (they happen when there are multiple uninstalls + installs of the extension), but the saveToken errors seem relevant. Is there any more information from them (the stack trace, usually)?

@brn - I'm at the edge of my debugging knowledge, and I couldn't get a stack trace. As a feeble attempt to assist, this is what I found:

1. The following error is the only one that pops up the moment the API key is lost. This is seen in the Firefox "Browser Console":
   Could not establish connection. Receiving end does not exist.
saveToken moz-extension://e208da21-d8c9-4e89-bb50-1c2658f797a6/src/background.js:66

2. If I go to Firefox "about:debugging#/runtime/this-firefox", and turn on the developer tools for the extension, The following repeat warning appears in the console window after a few minutes:
   Background event page was not terminated on idle because a DevTools toolbox is attached to the extension.

3. While that developer tools console window is open, the API is NEVER lost. It works perfectly. Once that console window closes, the API key is lost after a random amount of time browsing.

4. Also, in the "Storage" tab of the extension developer tools, the Extension Storage section shows correct values for api_token, api_engine, session_token and "sync_enabled" as "false". When the API key is lost, api_token and api_engine is undefined, session_token is correct, but now "sync_enabled" is "true".

That's the best I have. Happy hunting!

Thanks @KGuser ! When you see that error in the console, it should be possible to click in the error and get some more information about the trace. If you can't get that, it's fine, though.

Thanks @brn . Clicking on the saveToken error, takes me to this section of the extension's background.js

// tell the extension popup to update the UI
await browser.runtime.sendMessage({
type: 'synced',
token: sessionToken,
api_token: sessionApiToken,
api_engine: sessionApiEngine,
summary_type: sessionSummaryType,
target_language: sessionTargetLanguage,
});

Specifically the "await browser.runtime.sendMessage" line is highlighted. Not sure if this is what you need.

Ok, that does seem to mean the extension is closed before it reaches that point, which is weird, but I suppose I can work around it, as it's not the saving that's wrong, it's the asking the extension's UI to show the locally saved values that's failing.

v0.5.0 should still help with this as per https://github.com/kagisearch/browser_extensions/pull/62