-
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
Swift 6 Mode breaks the LaunchDarkly SDK #419
Comments
Thank you for reporting this. We will investigate. |
Hi @choulepoka, I have been unable to reproduce this issue. I tried with XCode 16.2, Swift 6, and a simulator running 18.2. Would you be willing to make a minimal reproducible project? Getting it to happen in our hello-ios-swift may be an option. |
Hi @tanderson-ld ! Sorry for the delay. I have created a fork of the hello-ios-swift project and adjusted it to reproduce the bug https://github.com/choulepoka/hello-ios-swift The issue seems to occurs when I set the minimum iOS version to 15 (up from the project's original iOS 12) Cheers! |
Thank you for taking the time! When I have a moment I will check that out. |
@tanderson-ld Hello, I am experiencing a crash in this same method, only when running under Swift 6. I have determined it occurs for me only when the |
Describe the bug
When enabling Swift 6 and invoking
LDClient.identify(context:timeout:completion:)
, the program will hard crash.To reproduce
Swift Language Version
build settingsExpected behavior
The call succeeds
Logs
Library version
9.12.0
XCode and Swift version
Code 16.2, Swift 6, iOS Simulator 18.2
Platform the issue occurs on
iPhone, iPad & Mac Catalyst
Additional context
For the
LDClient.start(config:context::startWaitSeconds:completion:)
, the completion is nillable, so by specifying nil, this call does not crash. But if you add a completion handler, it will hard crash.The text was updated successfully, but these errors were encountered: