Closed TasikBeyond closed 1 month ago
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% The platform spread does roughly align with the general user base. There are 19 events over the last seven days. Each from a unique user.
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 LDContext
from a few properties in our UserInfo object.
Our start method looks something like this.
private func start(_ userInfo: UserInfo?, completion: (() -> Void)? = nil) {
let config = LDConfig(mobileKey: AppConfiguration.LaunchDarkly.mobileKey, autoEnvAttributes: .enabled)
let context = buildContext(userInfo: userInfo)
LDClient.start(config: config, context: context, startWaitSeconds: 10) { [weak self] _ in
guard let self else { return }
if let userInfo {
self.sharedThreadsIsOn = isOn(flag: .sharedThreads, userInfo: userInfo)
}
LDClient.get()?.observe(key: LaunchDarklyFeatureFlag.sharedThreads.rawValue,
owner: self,
handler: { [weak self] flag in
self?.sharedThreadsIsOn = flag.newValue == true
})
completion?()
}
}
Which is called during didFinishLaunchingWithOptions
from our AppDelegate. We will also continue to investigate this area as a potential cause. Thank you.
Hi @TasikBeyond we are also getting this crash. Around 800 users getting the crash, which is a low percentage of our user base but is our current biggest crash right now.
Crashed: com.apple.root.default-qos
0 libswiftCore.dylib 0x4065b4 swift_isUniquelyReferenced_nonNull_native + 38
1 UNiDAYS 0xbddf3c specialized static ObjcLDClient.start(configuration:context:completion:) + 596 (LDClient.swift:596)
2 UNiDAYS 0xbdd240 @objc static ObjcLDClient.start(configuration:context:completion:) + 4382528064 (<compiler-generated>:4382528064)
@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