Brazekit not initialzied when loaded from cache during async call of MParticle.sharedInstance.Start()#771
Closed
ianhowertonmcd1 wants to merge 1 commit into
Conversation
4 tasks
Collaborator
|
Thank you for bringing this issue to our attention. I believe it was obscured by many of our other clients initializing Braze manually and most other kits no longer using the 'start' paradigm. We've implemented a change in the same vein as your fix and merged it to go out in our next release. |
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
2 participants
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.
Call kitInstance.start when loading a cached kit