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

No notifications with Snarl 5.0 #12

Open
steve-tregidgo opened this issue Jun 11, 2019 · 4 comments
Open

No notifications with Snarl 5.0 #12

steve-tregidgo opened this issue Jun 11, 2019 · 4 comments
Assignees

Comments

@steve-tregidgo
Copy link

Hi! I've installed the following on a new laptop:

  • FooSnarl 2.0 beta
  • foobar2000 v1.4.4
  • Snarl 5.0 (V47.120)

No notifications are reaching Snarl from FooSnarl.

  • Within the "Foobar2000" app in Snarl, the "Test" link shows a notification.
  • Within foobar2000's Advanced Settings for FooSnarl, the Test button does not show a notification.
  • When foobar2000 starts, Snarl shows a message with the heading "Application authentication error": Application "Foobar2000" was previously registered using a different password. Snarl has allowed the application to re-register, however you should contact the vendor and ask them to modify their application.

This worked on my previous laptop (with foobar2000 1.3.10 and Snarl 3.1). I may be able to downgrade Snarl but am hoping FooSnarl can be made to work with this combination.

I don't know where else I might find useful logs but am happy to dig into them if somebody can tell me where to look.

Thanks,
Steve

@pyrodogg
Copy link
Owner

pyrodogg commented Jun 11, 2019 via email

@pyrodogg pyrodogg self-assigned this Jun 24, 2019
@pyrodogg
Copy link
Owner

I've been able to reproduce this behavior. I'll dig into the Snarl 5.0 documentation to see what's updated. It looked like Snarl 5 has legacy support for older notification protocol versions, but it'll be good to have it naively working with V5 anyway.

@steve-tregidgo
Copy link
Author

Thanks Pyro! I appreciate you digging in.

@Tenome
Copy link

Tenome commented Mar 1, 2023

Was this ever fixed, or should I downgrade?

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

No branches or pull requests

3 participants