fix: defer AdobeMedia one-time init until launchAppId is available#32
Merged
Conversation
Guard the start path before dispatch_once so a missing launchAppId does not consume the one-time initialization block. This allows AdobeMedia initialization to run when configuration arrives later in the same process.
nickolas-dimitrakas
approved these changes
Apr 30, 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.
Background
AdobeMedia startup could consume its one-time initialization path before
launchAppIdwas available, preventing later initialization in the same process. This update ensures initialization is attempted only when configuration is present.What Has Changed
launchAppIdguard before entering the one-time initialization blockdispatch_oncefrom executing in unconfigured startup statesScreenshots/Video
N/A
Checklist
Additional Notes
MPKitAdobeMedia.start.