-
Notifications
You must be signed in to change notification settings - Fork 83
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
EXC_BAD_ACCESS KERN_INVALID_ADDRESS on LDClient.start #373
Comments
Hello @TasikBeyond , thank you for reporting this and thank you for the percentage breakdown of the platforms. Does that roughly match your userbase? What percentage of sessions is this happening in? Do you have the number of occurences? |
Hey @tanderson-ld It's a very low percentage of sessions. ~0.01% |
Thank you for that data, helps to eliminate some possibilities. We're actively looking at this today and I will let know you what we find. |
Did you use a version prior to this version without issue? If so, what version was that? Thank you. |
@TasikBeyond , is the UserInfo a class in your codebase? Do you reference an instance of it in the LDClient.start(...) completion callback? Theory right now is that the start completion in your code base is a spot to investigate. |
Hey @tanderson-ld thank you for looking into this. There was no prior version, we've recently added the SDK to our project. UserInfo is a class in our codebase. We build and return an Our start method looks something like this.
Which is called during |
Hi @TasikBeyond we are also getting this crash.
|
@Reedyuk, thank you for providing some more info for this issue. Is this actually the same crash or the same exception type? |
yes it looks different, i will raise seperately. |
@TasikBeyond , have you found anything out during investigation? At the moment we don't have any further actions we intend to take for this issue. |
Negative. Feel free to close and I'll reach out if I find something more concrete. Thank you! |
Thank you for letting us know and keep us posted. |
Describe the bug
Firebase crashlytics is capturing a bad access exception on a small percentage of our sessions.
To reproduce
Haven't reproduced locally.
Expected behavior
No crash.
Logs
Library version
LaunchDarkly 9.6.2
XCode and Swift version
Xcode 15.3 and Swift 5
Platform the issue occurs on
93% iPhone and 7% iPad
66% iOS 17
27% iOS 16
7% iPadOS 17
33% In Background
The text was updated successfully, but these errors were encountered: