5

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.

        a month later

        brn
        It seems to work as intended at the moment with v0.4.3. Many thanks.

        • brn likes this.

          Kagi for Firefox 0.5.0 released, please confirm if the issue is fixed.

            Yes, I confirm that the issue has been fixed. Thanks everyone.

              5 months later
              7 days later

              Saw the update came through, thanks Kagi team!

                No one is typing