-
Notifications
You must be signed in to change notification settings - Fork 244
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
Crashes on -[CountlyPersistency serializedRecordedEvents] #374
Comments
Hello @agroelfe, Thank you for reporting this issue. To investigate and resolve the crash effectively, I’d like to request the following: Segmentation Details: Could you please clarify what segmentation data is being sent? Specifically, if there are custom fields or unexpected large payloads, this will help us identify any issues in the data being serialized. Crash Reproduction: If possible, could you enable debugging in your app and attempt to reproduce the crash? This will allow us to pinpoint the root cause more effectively. And also too see the crash in details we need to see non-symbolicated stack trace. To enable debugging in the SDK, please use the following configuration during initialization: Plase share the logs captured from the moment the SDK is initialized until just after the crash. These logs will provide valuable context for understanding what happened prior to the error. Once we have this information, we’ll be able to dive deeper into the issue and provide a resolution promptly. Looking forward to your response. Let me know if there’s anything else I can do to assist! |
Hi, @arifBurakDemiray!
var params: [String: String] = ...
if let duration = event.duration {
Countly.sharedInstance().recordEvent(event.key, segmentation: params, count: 1, sum: 0, duration: duration)
} else {
Countly.sharedInstance().recordEvent(event.key, segmentation: params)
} We do not exceed 10 parameters per event (I guess even 8), very most of them are short string values of swift enumerations in our codebase, with few exceptions having a URL in a
|
Hi @agroelfe, Thank you for sharing the details about the crash and your usage patterns! I understand how tricky these issues can be, especially when they're hard to reproduce on your end. I'll also dive deeper into this issue and attempt to reproduce the crash on my side. In the meantime, I'll review the crash logs you provided and investigate potential edge cases in the SDK that could lead to a SIGSEGV. If you do manage to reproduce the crash and can share the Countly debug logs, it would help narrow down the root cause significantly. I'll keep you updated on my findings as I work through this. Thanks for your patience, and let me know if there’s anything else I can assist with in the meantime! |
Dear Countly Team!
I regret to report my app is having several crashes ending with similar crash logs:
Crash 1
Crash 2
Crash 3
Environment
Countly versions: 24.7.9, 23.8.3
iOS Versions: 18.x, 17.x
Countly config:
A Device ID is changed to user-specific one in runtime via
Countly.sharedInstance().changeDeviceID(withMerge:)
.Can you, please, help me find a workaround for this or fix it?
The text was updated successfully, but these errors were encountered: