The VideoLAN Forums

Something strange has just started happening today....

I use VLC as my player to stream music from a WLAN. When it opens up it (till today) automatically starts streaming the audio after pressing selecting to "play" the URL not "Download" it from the popup.. But for some reason today on 2 different Apple devices, the only way for it to start playing is to swipe up my Iphone/Ipad screen - making the shortcut to Aeroplane mode, Bluetooth, Sleep etc icons appear - then dismiss those icons. I then have to swipe upwards again and the player starts .

Any ideas why? Or how to fix?

This should be resolved in today's update. Thanks for reporting

Hi Paul,

Thanks for your reply..

Just back from holidays and I installed VLC on a different Iphone today (18 Aug) and the same problem occurs I'm afraid. To check, I have deleted VLC player from my Iphone and re-installed and the same issue is there.

Any ideas??

Many thanks in advance..

Could you check in the cone menu, last entry, whether your installed version is 2.6.4?

Yep, 2.6.4(1) installed. Based on:2.2.2 Weatherwax

Just to chime in, I'm having the same issue. I'm launching via links in safari formatted as "vlc://<http stream url>". Launching streams like this hasn't worked for the past ~month. Using iOS8 and vlc 2.6.4.

Sorry for the delay. A bug fix release is awaiting review now.

If you are deploying the vlc:// pseudo protocol in a web app or third party iOS app, I highly encourage you to switch to the x-callback-url protocol which offers more features and behaves correctly with the current release. You can find details here: https://wiki.videolan.org/Documentation ... llback-url

I tried that as well and it also isn't working. It could be that I'm formatting it incorrectly, though. My url looks like this:

vlc-x-callback://x-callback-url/STREAM?url=<http stream url>

When I use that style of link, it opens VLC but then remains on the "Empty Media Library" screen. I've verified that the stream URL works by manually opening it in VLC on OSX.

I do look forward to being able to use x-callback-url, though. The x-error param will be very useful for specifying fallback streams in the particular app I'm building.



EDIT: I lowercased "stream" and now it's working.

Thanks Felix.

Great to hear. Note that if you add additional parameters, you need to encode the individual URLs