Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"NativeMessagingInterface has stopped working" #28

Open
WozardGit opened this issue Feb 3, 2017 · 5 comments
Open

"NativeMessagingInterface has stopped working" #28

WozardGit opened this issue Feb 3, 2017 · 5 comments

Comments

@WozardGit
Copy link

WozardGit commented Feb 3, 2017

Hello, thanks for this great tool!

I formatted my PC and are now experiencing issues when trying to use Google Play or SoundCloud.

When use the "Now Playing Companion" while having "Essential Now Playing" open, I get this: "NativeMessagingInterface has stopped working"

The program works fine with Winamp, and "NativeMessagingInterface.exe" is in the same folder as "Essential Now Playing.exe" with "settings.json" and "manifest.json"

I've tried to delete everything related to Essential Now Playing, including the Companion, and gotten the latest release, but no success.

What could the issue be?

@slimeyz
Copy link

slimeyz commented Jun 11, 2017

Having the same issue, after allowing access to file URL's in the extension settings, this error popped up. But this was the only way to allow SoundCloud to pick up on the song information.

@hanmun
Copy link

hanmun commented Jun 20, 2017

Having the same issue when trying to use with Google Play.

@pendo324
Copy link
Owner

Sorry it took me so long to respond, but @hanmun just brought this issue to my attention again and we were able to resolve it by following these steps (as you can see in #40):

  1. Close the Essential Now Playing desktop application
  2. Open up task manager and end the "NativeMessagingInterface" process
  3. Try running Essential Now Playing again and using the Google Play option

Let me know if you have any questions or if some of my instructions don't make sense. Thanks!

I plan on updating the application so that this isn't necessary, but that will have to wait until this weekend.

@hanmun
Copy link

hanmun commented Jun 21, 2017

@pendo324 @slimeyz @WozardGit Yes, manually ending the NativeMessagingInterface.exe process did it for me. Also, make sure that you have the extension up and running on the source you want before re-opening the desktop app or you'll just get the same error and you'll have to do it again.

@senpos
Copy link
Contributor

senpos commented Jun 25, 2017

I am not sure if my problem is related to this issue, but i noticed, when i close app and remove companion from Chrome - NativeMessagingInterface starts to consume a lot of processor time.

Screenshot

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

No branches or pull requests

5 participants