gaqzi / chrome-open-in-spotify-client Goto Github PK

Summary

Version on chrome extension store is still using 1.3 that no longer works

Are there any plans to update this to 1.4.1?

The extension works great w/ all open.spotify.com links I've tested but when it tries to load an embedded playlist from the web into the desktop player I get this error:

"There was a problem displaying this view! This view either does not exist or an error has occurred." If I disable the extension the playlists load on the web site as expected.

Here are a couple examples:

https://www.reddit.com/r/spotify/comments/8opjis/back_to_the_80s_i_best_of_synthwave_and_retrowave/

https://www.reddit.com/r/spotify/comments/8ou5qh/mf_doom_48_timeless_songs_from_my_favorite_hiphop/

Hi,

First of all, thank you for this amazing extension. The extension shouldn’t be necessary in the first place but I’m thankful that it exists!

The issue

I’m on Chrome 67 on macOS Sierra. Just after installing the extension for the first time, I noted that opening a open.spotify.com link would seem to bring Chrome to the front but never open Spotify.

Analysis

A little debugging reveals that the redirect does work (in the sense that Chrome displays a modal pop-up in the new tab, asking for permission to open the Spotify app); however, the 100 ms timeout causes the current tab to be closed automatically before I even get to see that pop-up.

You can check this setting by locating your Preferences file (mine is in ~/Library/Application Support/Google/Chrome, on Windows the file seems to be in %LOCALAPPDATA%\Google\Chrome\User Data\Default) and looking at the .protocol_handler.excluded_schemes entry there. If .protocol_handler.excluded_schemes contains a spotify key with a value of false, Chrome will never ask for permission for the Spotify protocol handler. Otherwise, it will always ask for permission, which is the default.

That means the extension may not work for anyone who has never opened a spotify: link before nor ticked the never-ask-again box in the popup.

Proposed fix

No idea yet.

I’ve tried to use the navigationRequest, tabs, and webRequest APIs to emulate some kind of redirection-complete event but didn’t succeed.

Workaround

At the very least, I’d suggest to add a Known issues section to README.md with the following description:

If the extension appears to do nothing for you, type spotify: in the browser and hit Enter. Tick the box to allow Chrome to always open Spotify without asking. Finally, click Open Spotify to confirm.

I have installed Spotify on Ubuntu 18.04 via the OS's store, which by default now installs a snap. There's two issues I'm experiencing, which may have to do with the fact that it's a snap:

• the plugin launches a new Spotify instance every time a link is opened (instead of using the existing spotify instance)
• the right playlist/album/artist isn't opened; it just launches Spotify's home screen

Not sure if you're able to support this at all, or if this would require action from Spotify's side. Thanks in any case for your work on this :)

I don't think the app is accepting these parameters anymore.

https://www.whosampled.com/sample/66079/Amon-Tobin-People-Like-Frank-Angelo-Badalamenti-Night-Streets-Sandy-and-Jeffrey/

Hi, just letting you know I'm not able to get this link to load in Spotify. The track on the right by Angelo Badalamenti has a Spotify link but will neither play in Chrome nor open the desktop app.