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
Notification does not show using keyboard shortcut when app first starts #19
Comments
This happens because Spotify Notifications gets song information from notifications sent by Spotify when the play state changes (i.e when a track begins playing or is paused). So, if Spotify begins playing a song before Spotify Notifications is started, Spotify Notifications misses the notification from Spotify and produces a notification with no content - which is why it doesn't popup. As you noted, if you play/pause/skip after opening Spotify Notifications, everything works. Depending on how much you use Spotify (and Spotify Notifications), I'd recommend just having it start on login. In addition, I'll implement a check so that empty notifications are not produced. |
@citruspi That makes total sense. Thanks so much for clearing that up, cause I was definitely confused at first. I've been using SizzlingKeys for years and it produces a 'No Song Playing' toast if iTunes is closed or it just has no information. |
I personally rely on the keyboard shortcut to see what song is playing at On Thursday, May 1, 2014, Mihir Singh notifications@github.com wrote:
Cheers, |
I've added a few lines of code which will produce a notification when the shortcut is activated even if there is no song information recorded. It will be included in the next release (which will be before June 02), but if you want it before then, feel free to clone and build the project yourself. If you do build it yourself, please let me know if you have any issues. Thanks. |
Thanks again, you're awesome Mihir. |
Environment
To reproduce:
What I get:
If I open Spotify Notifications first or skip to the next song after opening Spotify Notifications then everything seems to work fine.
The text was updated successfully, but these errors were encountered: