fix: Prevent Start When Configuration Not Set #62
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
thomson-t
approved these changes
Jul 16, 2025
BrandonStalnaker
deleted the
fix/SQDSDKS-7497-Prevent-Start-When-Config-Not-Set
branch
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.
Reference
SDK-7497 -- Prevent Start When Configuration Not Set.
Summary
A race condition appears to be affecting the Branch SDK initialization process. Specifically, when a user updates the app from version 8.1.1 to greater, the Branch SDK attempts to initialize unseccesfully altough the Branch Key appears to be ready to use. This results in improper or failed initialization. This issue does not occur on a fresh install.
Type Of Change
Testing Instructions
cc @BranchMetrics/saas-sdk-devs for visibility.