-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Ti.Media.VideoPlayer could support HTTPS streaming? #14073
Comments
For Android please check: https://github.com/m1ga/ti.exoplayer |
Thanks for the link! The main problem remains iOS which tends to crash on HTTPS. I see that you have a great repository of beautiful modules, I have watched them one by one carefully. I give you all my compliments for your work! I am a Titanium enthusiast of the first hour, my first App in the store still goes back to before Axway (2014), to when push notifications were managed from the web panel of the site. |
You're welcome and thanks 😄 I mostly do Android work that's why I had that module and infos ready. I have no clue about the iOS part and since you've selected So hopefully an iOS developer is checking the iOS part |
I'll check this |
For iOS it is possible to convert the video to HLS format and stream it via HTTPS I suppose.
And this should play on iOS via HTTPS. (Not tested at the moment) |
I have searched and made sure there are no existing issues for the issue I am filing
Description
At the moment the VideoPlayer do not fully support HTTPS video streaming, and trying to play an HTTPS video could crash your app.
This could also be one of the main reasons because ATS (Apple Transport Security) is disabled by default.
Could it be possible to implement HTTPS streaming in future versions?
Solution
Implement VideoPlayer HTTPS video streaming.
Alternatives
On iOS: Prefetch the video with Ti.Network.HTTPRequest and inject it in the player via the media attribute.
On any: Prefetch the video with Ti.Network.HTTPRequest and store to local file.
Platforms
Android & iOS
The text was updated successfully, but these errors were encountered: