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

Spotify part of Snip not working any more with new Spotify update #300

Closed
sapphonie opened this issue Jul 20, 2018 · 10 comments
Closed

Spotify part of Snip not working any more with new Spotify update #300

sapphonie opened this issue Jul 20, 2018 · 10 comments

Comments

@sapphonie
Copy link

title.

cant provide any logs or whatever because i dont know where they are or if they even exist, sorry

tried restarting computer, restarting snip, and restarting spotify, all in various orders, nothing resolves the "no track playing" message with Snip.

any fix?

@TheRylez813
Copy link

I am also having this problem.

@neverbackdown81
Copy link

im also haveing the problems snip latest version wont do anything now just says no track playiing even tho spotify is running

@happymintyo
Copy link

same here. its not writing anything into Snip.txt or Snip_Artwork.jpg

@florenzius
Copy link

Same problem. Please fix!

@pswaab
Copy link

pswaab commented Jul 20, 2018

Hi Same here,

After spotify updated it seems not working anymore, so probably something closed by Spotify.
Hopefully there will be a fix soon.

Kind regards Patrick

@Levadio
Copy link

Levadio commented Jul 20, 2018

same problem fix it pls.
i have try the old version but don´t work

@markspolakovs
Copy link
Contributor

markspolakovs commented Jul 20, 2018

sigh Duplicate of #300, #299, #265, #283.

Is typing "spotify" into search really that hard?

@sapphonie
Copy link
Author

sapphonie commented Jul 20, 2018

#300 is a dupe of #300? lol

edit: anyway, i opened this because snip broke for me with the newest spotify update. i was wondering if there was any fix in the works for this, because i use snip for my stream on twitch.

edit edit: also this isnt a dupe of #299, if you actually read the whole issue report including all the comments....

edit edit edit: and youre the one who specifically said that "this is not the issue for you" etc. on that thread?? 🤔

@sapphonie
Copy link
Author

anyway closing and saying for any other future visitors: go to #265

@markspolakovs
Copy link
Contributor

markspolakovs commented Jul 21, 2018

@TheSqrtMinus1 I think I meant to comment this on 301, oops.

In general though, there's no point in opening a new issue just because it doesn't work for you if there are at least four other people reporting the exact same problem - for the developer it's just duplicate information, and they waste time reading through issues of people reporting the same thing in the hope that there's some new information. "me too pls fix" is the most useless comment one could ever post on an issue. The developer - and everyone who's commented on it - gets an email, they check if in the hope of there being new information that could help diagnose the problem and fix it, but they only get frustrated.

My sincere apologies if I seem harsh, however I hope you get where I'm coming from.

If you're having the same problem, use the GitHub reactions feature to add a 👍 reaction, instead of commenting "me too pls fix" (which some people have literally commented) or opening a new issue.

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

8 participants