Release - #463
Merged
Merged
Conversation
theoplayer-bot
Bot
force-pushed
the
changeset-release/main
branch
from
August 17, 2026 08:39
c9affd8 to
77a926f
Compare
tvanlaerhoven
self-requested a review
August 17, 2026 08:43
tvanlaerhoven
approved these changes
Aug 17, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@theoplayer/react-native-analytics-adobe-edge@1.3.1
🐛 Issues
media.bitrateChange) would fail with "Session ID is not available for playerId" when the media session start was not yet confirmed by the edge network. The session is now only marked as started after confirmation, failed session starts are retried, and tracker promise rejections no longer surface as unhandled promise rejections.loadedmetadataevent fired before the Adobe media tracker was initialized.adStartandadCompletewith a 400 Bad Request ("Playhead must be in range [0, 86400] seconds") during live playback on platforms that report the playhead as an absolute presentation timestamp (e.g. Samsung Tizen). The playhead is now always clamped to the range accepted by the API.