-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Completion invoked twice #428
Comments
It seems like the assumption here is that the closure passed to However, if (1) the closure passed to In our case, we're passing 10 for startWaitSeconds. |
Thank you @macdrevx, taking a look. |
We have merged a fix in #429 and will be releasing that shortly. Thank you again for investigating and helping us hone in on that spot of code. Which version of the SDK are you using? |
Thanks! We're on 9.12.0 |
Also, I left a small suggestion on that pr: https://github.com/launchdarkly/ios-client-sdk/pull/429/files#r1953291290 |
Your suggestions are absolutely valid. I thought about that while making the tweak, but wanted to minimize impact risk. I'll keep those in mind if I touch that code in the future. 9.12.3 was released with the fix and should be propagating through the package distribution systems. |
We wrap
LDClient.start
inwithCheckedContinuation
and we have a crash stemming from the continuation being invoked twice. Looking at the implementation, I'm pretty sure there's a race condition here that permits the completion block to be invoked more than once:ios-client-sdk/LaunchDarkly/LaunchDarkly/LDClient.swift
Lines 836 to 849 in cb270ec
The text was updated successfully, but these errors were encountered: