[iOS] ManagedPlayer only unload context on state changes, not when player disappears #137
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.
The changes to use JSVirtualMachine by default changed to unload player when it disappeared. Some presentation contexts over ManagedPlayer would trigger onDisappear unintentionally unloading player.
Switch to explicitly unload context on state changes for ManagedPlayer, rather than when SwiftUI disappears
Version
Published prerelease version:
0.4.0-next.7
Changelog
Release Notes
sync up to latest (#131)
Sync latest code
Expose utils for expression LSP (#117)
parseExpression
from the expression parserstrict
flag toparseExpression
that will (when disabled) attach any parsing errors to the top-level node instead of throwingDeps/bump dependencies (#111)
Dependency upgrades
Sync Latest Player Code (#109)
Syncs to latest version and bumps tapable-ts to latest version.
🚀 Enhancement
🐛 Bug Fix
Authors: 7