chrome-for-testing - NativeMessagingHosts locations (macOS)?

[Salmin Skenderovic]

Hi,

Recently chrome removed the --load-extension flag from chrome, which forced us to migrate our tests to chrome-for-testing. We use cypress which opens chrome-for-testing as system user.

For chrome these are the locations we used:

system: /Library/Google/Chrome/NativeMessagingHosts

user: ~/Library/Application Support/Google/Chrome/NativeMessagingHosts

For chrome-for-test I added the manifests in these locations:

system: /Library/Google/Chrome for Testing/NativeMessagingHosts

user: ~/Library/Application Support/Google/Chrome for Testing/NativeMessagingHosts

It seems like the user level manifest works, but when I tried running cypress I keep getting "Unchecked runtime.lastError: Specified native messaging host not found."

(the manifest com.company.org.json file has been copied into all 4 locations so it is identical). 

[Salmin Skenderovic]

Update: this is not limited to cypress. If I run chrome-for-testing as sudo, I can't use the NativeMessagingHost.

I tried running it with `--enable-logging --v=1` but it doesn't show anything of value

[Oliver Dunk]

Hi Salmin,

Currently, Chrome for Testing loads the manifests from /Library/Application Support/Chromium.

We should probably fix that, and I have a bug open for it here: https://issues.chromium.org/420443624

Hopefully that helps in the meantime!

Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, GB

--
You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/c5309374-f6d0-4d54-9826-366b4f485f67n%40chromium.org.