Feature/ iOS: Send actual player state with onPlayerReady event #615
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@wvanhaevre this is just our implementation from the patch, pls feel free to change the code along with your guideliness 👍 |
…er into payload-onplayerready-event * 'develop' of github.com:THEOplayer/react-native-theoplayer: (67 commits) 9.10.0 Update changelog Add changelog entry Update state's currentTime on seeking seeked events Fix seeking seeked event types Add changelog entry Fix attaching seeked handler Update iOS github action Update connector list Remove unsused import (Platform) Remove $ from copyable code blocks Add `,` in "features" array react-native init is deprecated Starting from v0.71 Typescript is used by default Add changelog entry Do not reparent on transitioning Update layout on transition Fix player fullscreen layout 9.9.1 Prepare changelog for release update example pod lock Add changelog entry ...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This should help us to implement seamless backward transition from floating container to regular JS tree. Android already sends this data in event payload, it just makes it consistent between two platforms.
Test-plan: