-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Cannot stream a video from PFFile URL iOS #692
Comments
Can you access the URL in your browser? http://stackoverflow.com/questions/tagged/parse-server is another place you can ask this question. |
Yes I can, I can watch the video using Google Chrome with the exact same link I try to use with heroku and parse server, yet on iOS it doesn't work? |
Hi, I tried to access your video link in chrome it is not working. Also Can you try streaming your video with https link ? Does your iOS project accept http links ? You might need to add some settings in your ios project to accept non-ssl urls. |
Hi, First that is a fake link because the video was a bit of a personal one. Second I know it accepts https because when I use Parse (The one that is closing down, not a custom server) it streams perfectly and is a https link. |
Can you get us any video with a working link? |
Is that the correct link with appname ? |
Doesn't seem to be, that's why I asked for a full link. |
Closed for lack of activity. |
Hi, Same problem here. Parse server on AWS ElasticBeanstalk cannot stream mp4 pffile saved on mongoDB on AWS EC2. Video plays on chrome but does not play on Safari or iOS app. Videos hosted on parse service play with no problem. iOS error: Error Domain=AVFoundationErrorDomain Code=-11850 "Operation Stopped" UserInfo={NSUnderlyingError=0x13fb86740 {Error Domain=NSOSStatusErrorDomain Code=-12939 "(null)"}, NSLocalizedFailureReason=The server is not correctly configured., NSLocalizedDescription=Operation Stopped} Any help? |
Using the S3 file adapter fixed it! |
I have the same issue as well :( We currently are using the S3 adapter, setting the content-type, with no luck.... There is just a gray play button without anything playing. You can stream from a browser fine, but when trying to access it from iOS it's not working |
So, heroku+mlab support doesn't work anymore ? Only choice is to use heroku+S3 ? Doesn't mlab internally uses s3 for storing files. I'm not even sure whether parse-server supports streaming anymore. |
Not even trying to stream. Our application is fine downloading the content and playing, but still no luck. Anyone find any resolution yet? |
We are having the same issue with iOS. |
@manishsangwan Doesn't stream on iOS app or in iOS safari ? Because it does stream inside iOS app using Parse sdk for us & not in Safari OX/iOS . It streams fine in Chrome & Firefox. If feasible, can you host a sample file in S3 itself and point to it from parse server instead of mLab; as mLab seems to be the common variable in all these issues. |
[Solved] The solution is given by @Bragegs here - #1440 (comment) . In short, parse-server doesn't seem to be supporting streaming of audio/video and @Bragegs code enables it. I hope it get's PR and parse team looks into it. |
@indiandragon is there a solution for Google cloud storage? |
The solution is for gridstoreadapter. but its not working for S3Adapter. |
Use direct access and it should be ok. |
. |
Hello,
First of all, the code I use to try stream a PFFile video with its URL works %100 fine using Parse, however when I switch to using heroku I cannot stream the PFFile video.
When using the
AVPlayerViewController
it comes up with a crossed out play button.This is an example of what the url looks like from heroku -
http://appname.herokuapp.com/parse/files/appname/a5886e0be65d6fe59cace6c12113572c_file.mp4
Everything else works fine, saving photos as PFFiles and retrieving them and saving normal PFObjects.
It seems it might be something to do with the PFFile url is not recognised by the parse server api because it expects a different formatted string to the one heroku gives?
This issue has been here for about 2 months and still no fix. Any help greatly appreciated!
The text was updated successfully, but these errors were encountered: