API is not started by browsers

[ahizap]

The API is supposed to be started by browser after enabling the api in the setting but it's just not starting I left the browser open for 10 minutes, tried different browsers firefox and chrome, restarted browser even restarted windows. I'm pretty sure I have followed all the instructions faithfully but I don't know why it's not working. If you need any more details for debugging please tell me.

[ahizap]

This is the error log file that gets created after I run the bat file manually error.log it says crowbar file is missing but it is in the same directory and it's not empty either.

[ahizap]

I tried in linux and it's working I guess it's a windows issue.

[Kuuuube]

That file being missing shouldn't matter. It will always be missing on first run. I'll see if i can replicate on windows sometime.

[jacksonSingleton]

@Kuuuube Any update? I'm on macOS 26.2 (25C56) with Chrome Version 149.0.7827.54 (Official Build) (arm64)

Re-ran the installer. Manually checked the files in NativeMessagingHosts and verified that they look good. In Chrome, I see the following errors though:

Yomitan Popup Dictionary 26.5.19.0 has encountered a problem.
Originating URL: chrome-extension://likgccmbimhjbgkjambclfkhldnlhbnn/sw.js
TypeError: Failed to fetch
    at YomitanApi._updateRemoteVersion (chrome-extension://likgccmbimhjbgkjambclfkhldnlhbnn/js/comm/yomitan-api.js:557:36)
    at YomitanApi.getRemoteVersion (chrome-extension://likgccmbimhjbgkjambclfkhldnlhbnn/js/comm/yomitan-api.js:116:20)
    at async Backend._onApiTestYomitanApi (chrome-extension://likgccmbimhjbgkjambclfkhldnlhbnn/js/background/backend.js:1063:29)

Issues can be reported at https://github.com/yomidevs/yomitan/issues
logGenericError @ log.js:138
log.js:138 Yomitan Popup Dictionary 26.5.19.0 has encountered a problem.
Originating URL: chrome-extension://likgccmbimhjbgkjambclfkhldnlhbnn/sw.js
TypeError: chrome.runtime.connectNative is not a function
    at YomitanApi._setupPort (chrome-extension://likgccmbimhjbgkjambclfkhldnlhbnn/js/comm/yomitan-api.js:602:37)
    at YomitanApi._setupPortWrapper (chrome-extension://likgccmbimhjbgkjambclfkhldnlhbnn/js/comm/yomitan-api.js:589:43)
    at YomitanApi.startApiServer (chrome-extension://likgccmbimhjbgkjambclfkhldnlhbnn/js/comm/yomitan-api.js:125:24)
    at YomitanApi.setEnabled (chrome-extension://likgccmbimhjbgkjambclfkhldnlhbnn/js/comm/yomitan-api.js:83:24)
    at Backend._applyOptions (chrome-extension://likgccmbimhjbgkjambclfkhldnlhbnn/js/background/backend.js:1525:31)
    at Backend._saveOptions (chrome-extension://likgccmbimhjbgkjambclfkhldnlhbnn/js/background/backend.js:2701:14)
    at async Backend._modifySettings (chrome-extension://likgccmbimhjbgkjambclfkhldnlhbnn/js/background/backend.js:1318:9)

Issues can be reported at https://github.com/yomidevs/yomitan/issues
logGenericError @ log.js:138

[jacksonSingleton]

Ignore my previous message, just required a hard restart of all Chrome instances after installing (Not just the active profile that has Yomitan installed.) Odd, but similar issue found at:

Tampermonkey/tampermonkey#2501