Document PillarboxPlayer APIs as supported on the main thread only #932
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.
Description
This PR adds an important warning to PillarboxPlayer main documentation entry point, explicitly stating that corresponding APIs are supported from the main thread only. It also ensures that tracker lifecycle methods are called on the main thread, which was not guaranteed.
Calling PillarboxPlayer APIs from background threads is theoretically possible but requires some work, see #931. Until then it is best to warn developers about the current limitations, which should not change anything in practice (most public Pillarbox APIs are meant to be used from UI code anyway).
Changes made
Checklist