Crashed: OneSignal.OSOperationRepo

[Parthzobi]

Hey team,
Could you please check I'm getting a few crashes on Onesignal SDK.

"version" : "5.1.5"

Logs:

          Crashed: OneSignal.OSOperationRepo
0  libobjc.A.dylib                0x3020 objc_msgSend + 32
1  Foundation                     0x13a2c _encodeObject + 180
2  OneSignalUser                  0x11b48 __swift_destroy_boxed_opaque_existential_0 + 6928
3  OneSignalUser                  0x11ba8 __swift_destroy_boxed_opaque_existential_0 + 7024
4  Foundation                     0x13e14 _encodeObject + 1180
5  OneSignalOSCore                0xe5c4 __swift_destroy_boxed_opaque_existential_0 + 5632
6  OneSignalOSCore                0xe6d8 __swift_destroy_boxed_opaque_existential_0 + 5908
7  Foundation                     0x13e14 _encodeObject + 1180
8  Foundation                     0x137b4 -[NSKeyedArchiver _encodeArrayOfObjects:forKey:] + 460
9  Foundation                     0x27434 -[NSArray(NSArray) encodeWithCoder:] + 588
10 Foundation                     0x13e14 _encodeObject + 1180
11 Foundation                     0x199480 +[NSKeyedArchiver archivedDataWithRootObject:] + 104
12 OneSignalCore                  0xd69c -[OneSignalUserDefaults saveCodeableDataForKey:withValue:] + 88
13 OneSignalOSCore                0x7d30 __swift_instantiateConcreteTypeFromMangledName + 2856
14 OneSignalOSCore                0x75b8 __swift_instantiateConcreteTypeFromMangledName + 944
15 libdispatch.dylib              0x213c _dispatch_call_block_and_release + 32
16 libdispatch.dylib              0x3dd4 _dispatch_client_callout + 20
17 libdispatch.dylib              0xb400 _dispatch_lane_serial_drain + 748
18 libdispatch.dylib              0xbf30 _dispatch_lane_invoke + 380
19 libdispatch.dylib              0x16cb4 _dispatch_root_queue_drain_deferred_wlh + 288
20 libdispatch.dylib              0x16528 _dispatch_workloop_worker_thread + 404
21 libsystem_pthread.dylib        0x4934 _pthread_wqthread + 288
22 libsystem_pthread.dylib        0x10cc start_wqthread + 8

[nan-li]

Hi @Parthzobi apologies for the delayed response. Your particular stacktrace looks like one that was fixed in Release 5.1.6.

Closing out this issue due to staleness, and note we are actively investigating all newer crash reports.

[Parthzobi]

Hi Nan, Thanks so much for the update! Appreciate you closing the loop on this. Glad to hear it’s been addressed in 5.1.5 — I’ll make sure we’re on the latest version. Thanks again!

…

On Thu, Apr 17, 2025 at 9:16 PM Nan ***@***.***> wrote: Closed #92 <#92> as completed. — Reply to this email directly, view it on GitHub <#92 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AYENHDR7U2ZQMTUNQV5J3VL2Z7EDZAVCNFSM6AAAAAB3LGYSMOVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJXGMYDQMZZHAZTIOI> . You are receiving this because you were mentioned.Message ID: ***@***.*** com>

-- Best regards, Parth Patel iOS Developer