Skip to content
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

[iOS] Cannot change controls property after init #49

Closed
manijak opened this issue Dec 15, 2016 · 4 comments
Closed

[iOS] Cannot change controls property after init #49

manijak opened this issue Dec 15, 2016 · 4 comments

Comments

@manijak
Copy link

manijak commented Dec 15, 2016

I have this famous iOS issue 'Unable to simultaneously satisfy constraints' when using the VideoPlayer. I know this is a bug in the AVPlayer, but I cannot seem to get around it.

The way around it is to disable the showsPlaybackControls before attaching the video-source. Then enable it. I can see that you have implemented this in the plugin-code for ios. But the error is still present.

I get the video-source url from a service, so I change the controls property to true after the binding is set. But even then the controls are not shown, which tells med that perhaps controls property cannot be set after init?

I have also tried setting controls="true" in the xml, but then the above error appears when going fullscreen video.

@bnussey
Copy link
Contributor

bnussey commented Dec 15, 2016

Hey @manijak I was experiencing this issue myself and solved it as you said we have.

Are you running ng2?

@manijak
Copy link
Author

manijak commented Dec 15, 2016

I'm using vanilla {N}. Hmmm I see now that I have version 1.1.5 of the plugin (for some reason). Have no idea why it installed such a low version. Will try with 2.0.0.

@manijak
Copy link
Author

manijak commented Dec 15, 2016

Ok, tested with 2.0.0. Still the same, this happens when I press the Fullscreen icon, then it pours out the mentioned errors.

@manijak
Copy link
Author

manijak commented Jan 29, 2017

I am not seeing this issue anymore. Could be due to the recent updates, thanks.

@manijak manijak closed this as completed Jan 29, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants