Conversation
Prevent multiple replies and ensure init() Future always resolves
akshay-g-jadhav
approved these changes
Apr 24, 2026
cpandya25
approved these changes
Apr 24, 2026
snuricp
approved these changes
Apr 29, 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.
Prevent multiple replies and ensure init() Future always resolves
Summary by cubic
Guarantees the Flutter
init()Future always resolves on CleverPush initialization failure and prevents multiple MethodChannel replies. Addresses Linear CP-11157 to stop hangs and “already replied” errors.repliedguard to callreplySuccessexactly once across success and failure callbacks inCleverPushPlugin.CleverPush#handleInitializedwithsuccess: falseand a null-safefailureMessage.Written for commit c3f8a56. Summary will update on new commits.