Repository navigation
Can't play sound in Safari OSX #27
Description
SC.initialize({
client_id: [CLIENT_ID]
});
SC.get("/resolve", { url: "https://soundcloud.com/roywoodsofficial/drama-feat-drake" }).then(t => {
return SC.stream("/tracks/" + t.id);
}).then(sound => {
sound.play();
});
Works in Chrome and Firefox, but Safari 9.0.1 on OSX and Safari on iOS 9.1 are showing the following error message:
[Error] Failed to load resource: Request header field Accept-Encoding is not allowed by Access-Control-Allow-Headers. (216772566.json, line 0)
[Error] XMLHttpRequest cannot load https://api.soundcloud.com/tracks/216772566.json?client_id=2e2d678be10b5a5d2d62af34b194428e. Request header field Accept-Encoding is not allowed by Access-Control-Allow-Headers.
Using the SDK at connect.soundcloud.com/sdk/sdk-3.0.0.js as well as soundcloud 3.0.1 on NPM.
Reacted by Dmitry Iv.
Activity
[-]Can't play sound in Safari OSX[/-][+]Can't play sound in Safari OSX/iOS[/+][-]Can't play sound in Safari OSX/iOS[/-][+]Can't play sound in Safari OSX[/+]patrickjuchli commentedon Oct 29, 2015
The same example is working when using the SDK version 2 (without Promises of course).
jv2222 commentedon Nov 6, 2015
I got the same error. Any ideas on a workaround?
thomasrhiel commentedon Nov 11, 2015
+1
marlenesco commentedon Nov 16, 2015
+1
soundreactor commentedon Nov 29, 2015
+1
soundreactor commentedon Nov 29, 2015
this seems to be a server sided problem. in "Access-Control-Allow-Headers"
Accept-Encoding is missing.
workaround for me was to make a little php proxy and modify the soundcloud sdk 3.0.0:
r = new XMLHttpRequest,
r.open(t, 'https://mrvv.net/beta/proxy.php?url='+n, true), //make your own or use mine for the moment..
Overload119 commentedon Dec 7, 2015
+1
andratwiro commentedon Dec 23, 2015
+1
hiddebraun commentedon Dec 30, 2015
+1
ArthurRougier commentedon Jan 30, 2016
Any news on this one ? @janmonschke maybe ?
heysamtexas commentedon Feb 1, 2016
@soundreactor that is exactly what i did. :-)
karensg commentedon Feb 1, 2016
I am just using the APIs without the Javascript SDK and I have the same bug. This is just a bug in Soundcloud API. How can it be that this bug is there for so long?
lifter035 commentedon Feb 2, 2016
@soundreactor what exactly did you do in your proxy.php? load url as file contents? could you share maybe?
thanks
13 remaining items
andrefelipe commentedon Apr 30, 2016
+1
auggod commentedon Apr 30, 2016
I just set up a gist with my personal solution for this (simple express server + nginx proxy) https://gist.github.com/auggod/019aa5eee8ef618dcf65678e4649d8a7
vojkny commentedon May 10, 2016
+1
lukephills commentedon May 23, 2016
The headers sent using 3.0 sdk sends
http://api.soundcloud.com/resolve?url=someUrl&client_id=?????&format=jsonWhere as the 2.0 sdk sends
http://api.soundcloud.com/resolve?url=someUrl&client_id=?????&format=json&_status_code_map[302]=200Has anyone resolved this without proxying SC requests?
dy commentedon Jun 6, 2016
Oh, I was thinking something is wrong with xhr in safari.
@lukephills thanks for 2.0 sdk url. At least some backend-less workaround.
diurnalist commentedon Jun 9, 2016
👋
I took some time to investigate and fix this today. It will be published in version 3.1.2 of the SDK to both NPM and our connect.soundcloud.com asset hosting domain. I need to work with some others to make sure it goes live.
See #63 for the fix. If anybody has found an official bug report for this behavior in Safari, I'd love to see it. It is a bizarre behavior by the browser, but I wasn't able to find proof of it being recognized as a bug.
diurnalist commentedon Jun 9, 2016
Published as https://connect.soundcloud.com/sdk/sdk-3.1.2.js - I hope this fixes things for you all ❤️
andrefelipe commentedon Jun 9, 2016
Works for me! https://www.anzuclub.com
Thanks!
jv2222 commentedon Jun 9, 2016
Doesn't work for me. Same issue as before. You can see here...
http://techzinglive.com/page/1584/296-tz-discussion-in-the-ether
View in chrome and the player works and view in safari and it doesn't with the following error:
diurnalist commentedon Jun 10, 2016
@jv2222 The reason is that the code on that page does the following:
You should instead change this to:
The former example works on Chrome/Firefox because the SDK will transparently follow redirects when present. The /resolve endpoint performs a 302 redirect to a different API url. However, as we've seen with Safari, that doesn't work very well due to some strange CORS behavior. If you use the official
SC.resolvefunction, it has a workaround in place to solve this problem.I'm not aware of any other SoundCloud API endpoints that need redirects to function, so if you just change that one piece, it should start working. Hope that helps.
lukephills commentedon Jun 16, 2016
Hi @diurnalist, thanks for working on this issue, although the problem still occurs for me.
Loading a track from the SC API into web audio XHR still throws these errors:
jv2222 commentedon Jun 17, 2016
@diurnalist Dude, thanks, you nailed it!
diurnalist commentedon Jun 17, 2016
@lukephills without more information, such as a reproduction link, I'm afraid I can't diagnose any further. Can you open a new issue if and when you have more info? I'm going to lock this issue for now.