mirror of
https://github.com/AnanthVivekanand/spotify-adblock.git
synced 2026-04-26 21:15:53 +03:00
[GH-ISSUE #14] App works great, but nothing plays #10
Labels
No labels
cannot reproduce
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/spotify-adblock#10
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @plastikhub on GitHub (Aug 6, 2020).
Original GitHub issue: https://github.com/AnanthVivekanand/spotify-adblock/issues/14
Went through all instructions, everything seems to be working ok, except no song will play. Is this something to do with the login5.spotify.com being blocked?
@AnanthVivekanand commented on GitHub (Aug 6, 2020):
I think it is indeed related to that. This is essentially the same as issue #3, we tried to unblock login5.spotify.com and found that ads come through.
You can try and add
login5.spotify.comtowhitelist.js(more details in #3) but as I explain, I can't whitelist without breaking functionality for other users.@yrnehli commented on GitHub (Aug 15, 2020):
Seems like downgrading Spotify to version 1.0.80 or lower solves this problem. Once the older version of Spotify is installed, open up Spotify and then run this shell script to block updates.
@pseudobacon commented on GitHub (Jan 17, 2021):
Confirmed working after downgrading to 1.0.87.491
EDIT: Nope. Not working. Music plays, but the ads come up. Will try 1.0.80.474 next
@pseudobacon commented on GitHub (Jan 22, 2021):
The lower version works as in music plays, but ads creep in unfortunately
@yrnehli commented on GitHub (Jan 23, 2021):
Have a look at the workaround I made, been using it for a few months with no problems.
https://github.com/henryli17/macOsSpotifyAdblocker
@AnanthVivekanand commented on GitHub (Jan 24, 2021):
Alright, so this is a confirmed bug. Another workaround in addition to @henryli17's project is to use the builtin man-in-the-middle filtering, the instructions for that are at the bottom of the README. I've been using the mitm-proxy branch for several months and its been working with no flaws, so I decided to go ahead and merge it into master.
@AnanthVivekanand commented on GitHub (Jun 23, 2021):
From now on, using mitm.js is the recommended approach, so this issue is resolved.