-
Notifications
You must be signed in to change notification settings - Fork 47
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
Tip: play video file from Directory.data on iOS #134
Comments
@ArneTN i will have a look to implemented but i am travelling to end next week so not before |
Thanks. I don't consider it to be a big issue as it works on a real device. However, it would be great if this issue was identified in the docs/readme. I also saw that it was mentioned in a closed issue, but I missed that at first. Thanks for a great plugin! Regards, |
@ArneTN i come back to you as i start looking at it Can you explain me the |
Maybe he refers to unlocked display mode, basically it can be achieved by not setting the displayMode |
Sorry, the intention here was orientation based on device orientation (sensor). The documentation says "default: 'portrait'", so my parameter ("sensor") is a leftover from a series of trial-and-error. As PhantomPainX suggests, the correct behavior would probably be achieved by not setting the displayMode at all. I reckon the "sensor" parameter is just ignored in my case. |
@ArneTN @PhantomPainX thanks for the clarification. I will fix this 2 issues in the next release |
@ArneTN @PhantomPainX This has been fixed in 5.0.4-1. Can you check and close the issue after tests |
@ArneTN No reply from you so i assume it works so i close the issue |
This is more a tip, rather than an issue. I struggled a bit with playing video file from Directory.data on iOS, but it turned out it was related to the iOS Simulator.
In my app, I download video files to Directory.data (for offline use). The following code gave me the message "filePath not implemented" in the iOS Simulator. However, it worked perfectly on a real device.
Video.ts:
The text was updated successfully, but these errors were encountered: