Skip to content
This repository has been archived by the owner on Sep 7, 2024. It is now read-only.

Establish communication with browser #2

Closed
samhh opened this issue Feb 22, 2017 · 4 comments
Closed

Establish communication with browser #2

samhh opened this issue Feb 22, 2017 · 4 comments
Assignees

Comments

@samhh
Copy link
Owner

samhh commented Feb 22, 2017

No description provided.

@samhh samhh self-assigned this Feb 22, 2017
@samhh
Copy link
Owner Author

samhh commented Feb 24, 2017

Established communication with Firefox extension successfully: e85752b

I suspect that the reason Chrome has yet to work is related to the "allowed_origins" key in its host JSON. Need to figure out how to log the backend in Chrome to see what errors it's throwing, if any.

On that note: https://developer.chrome.com/extensions/nativeMessaging

On Linux and OS X, this log can easily be accessed by starting Chrome from the command line and watching its output in the terminal.

@samhh
Copy link
Owner Author

samhh commented Feb 24, 2017

^^ That was easy. For future reference:

$ /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome

@samhh
Copy link
Owner Author

samhh commented Feb 24, 2017

I think my guess was correct.

Failed to load manifest for native messaging host com.samhh.bukubrow: Failed to parse pattern "chrome-extension://hkfhplegmecfnmcmmgoaplkbokhfajck": Empty path.

@samhh
Copy link
Owner Author

samhh commented Feb 24, 2017

Boom! a1e040f

Missing a simple forward slash...

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant