[Bug]: Crash OSModelStore.add(id:model:hydrating:)

by ADMIN 51 views

[Bug]: Crash OSModelStore.add(id:model:hydrating:)

OneSignal is a popular push notification service used by many developers to engage with their users. However, like any other software, it's not immune to bugs and crashes. In this article, we'll investigate a crash that occurs when calling OSModelStore.add(id:model:hydrating:) in the OneSignal iOS SDK.

The crash occurs when the OSModelStore.add(id:model:hydrating:) method is called, causing the app to crash with an EXC_BAD_ACCESS error. The crash report indicates that the issue is related to a dictionary subscript setter in the libswiftCore.dylib library.

The stacktrace is as follows:

EXC_BAD_ACCESS KERN_INVALID_ADDRESS Crashed: com.apple.main-thread
0  libobjc.A.dylib                0x3c20 objc_msgSend + 32
1  libswiftCore.dylib             0xb249c Dictionary._Variant.setValue(_:forKey:) + 92
2  libswiftCore.dylib             0x5a620 Dictionary.subscript.setter + 520
3  OneSignalOSCore                0xbd68 OSModelStore.add(id:model:hydrating:) + 93 (OSModelStore.swift:93)
4  OneSignalUser                  0x77d8 OneSignalUserManagerImpl.setNewInternalUser(externalId:pushSubscriptionModel:) + 474 (OneSignalUserManagerImpl.swift:474)
5  OneSignalUser                  0x6864 OneSignalUserManagerImpl.createNewUser(externalId:token:) + 331 (OneSignalUserManagerImpl.swift:331)
6  OneSignalUser                  0x70dc OneSignalUserManagerImpl._login(externalId:token:) + 410 (OneSignalUserManagerImpl.swift:410)
7  OneSignalUser                  0x4af4 OneSignalUserManagerImpl.user.getter + 140 (OneSignalUserManagerImpl.swift:140)
8  OneSignalUser                  0xa4d8 OneSignalUserManagerImpl.setPushToken(_:) + 886 (OneSignalUserManagerImpl.swift:886)
9  OneSignalUser                  0xa5bc @objc OneSignalUserManagerImpl.removeAlias(_:) + 4346357180
10 OneSignalNotifications         0x6200 +[OSNotificationsManager sendPushTokenToDelegate] + 487 (OSNotificationsManager.m:487)
11 OneSignalNotifications         0x6030 +[OSNotificationsManager didRegisterForRemoteNotifications:deviceToken:] + 464 (OSNotificationsManager.m:464)
12 OneSignalNotifications         0x8aa4 -[OneSignalNotificationsAppDelegate oneSignalDidRegisterForRemoteNotifications:deviceToken:] + 118 (UIApplicationDelegate+OneSignalNotifications.m:118)
13 UIKitCore                      0x4bd18c __63-[UIApplication pushRegistry:didUpdatePushCredentials:forType:]_block_invoke + 96
14 libdispatch.dylib              0x2248 _dispatch_call_block_and_release + 32
15 libdispatch.dylib              0x3fa8 _dispatch_client_callout + 20
16 libdispatch.dylib              0x12a34 _dispatch_main_queue_drain + 984
17 libdispatch.dylib              0x1264c _dispatch_main_queue_callback_4CF + 44
18 CoreFoundation                 0x79bcc __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 16
19 CoreFoundation                 0x761c0 __CFRunLoopRun + 1996
20 CoreFoundation                 0xc8284 CFRunLoopRunSpecific + 588
21 GraphicsServices               0x14c0 GSEventRunModal + 164
22 UIKitCore                      0x3ee674 -[UIApplication _run] + 816
23 UIKitCore                      0x14e88 UIApplicationMain + 340
24 SwiftUI                        0x291ef8 closure #1 in KitRendererCommon(_:) + 168
25 SwiftUI                        0x291e28 runApp<A>(_:) + 100
26 SwiftUI                        0x291d0c static App.main() + 180
27 APP                         0x82e4 main + 52 (main.swift:52)
28 ???                            0x1c13e1de8 (Missing)

Unfortunately, the steps to reproduce this crash are not provided in the crash report.

The expected behavior is that the OSModelStore.add(id:model:hydrating:) method should be called without crashing the app.

The OneSignal iOS SDK version is 5.2.10.

The iOS version is 18.

No specific iOS version is mentioned in the crash report.

No relevant log output is provided in the crash report.

The Code of Conduct is not relevant to this issue.

In conclusion, the crash occurs when calling OSModelStore.add(id:model:hydrating:) in the OneSignal iOS SDK. The stacktrace indicates that the issue is related to a dictionary subscript setter in the libswiftCore.dylib library. Unfortunately, the steps to reproduce this crash are not provided in the crash report. To resolve this issue, we need to investigate further and provide a fix for the OSModelStore.add(id:model:hydrating:) method.

  1. Review the OSModelStore.add(id:model:hydrating:) method: Review the implementation of the OSModelStore.add(id:model:hydrating:) method to ensure that it is correct and does not cause any crashes.
  2. Check for dictionary subscript setter issues: Check if there are any issues with the dictionary subscript setter in the libswiftCore.dylib library that could be causing the crash.
  3. Provide a fix for the OSModelStore.add(id:model:hydrating:) method: Provide a fix for the OSModelStore.add(id:model:hydrating:) method to prevent the crash from occurring.
  1. Update the OneSignal iOS SDK: Update the OneSignal iOS SDK to the latest version to ensure that you have the latest fixes and improvements.
  2. Review the app's code: Review the app's code to ensure that it is correct and does not cause any crashes.
  3. Provide a fix for the OSModelStore.add(id:model:hydrating:) method: Provide a fix for the OSModelStore.add(id:model:hydrating:) method to prevent the crash from occurring.
  1. Investigate further: Investigate further to determine the root cause of the crash and provide a fix for the OSModelStore.add(id:model:hydrating:) method.
  2. Provide a fix for the OSModelStore.add(id:model:hydrating:) method: Provide a fix for the OSModelStore.add(id:model:hydrating:) method to prevent the crash from occurring.
  3. Update the OneSignal iOS SDK: Update the OneSignal iOS SDK to the latest version to ensure that you have the latest fixes and improvements.
    Q&A: [Bug]: Crash OSModelStore.add(id:model:hydrating:)

In our previous article, we investigated a crash that occurs when calling OSModelStore.add(id:model:hydrating:) in the OneSignal iOS SDK. In this article, we'll provide a Q&A section to help answer some of the common questions related to this issue.

A: The cause of the crash is related to a dictionary subscript setter in the libswiftCore.dylib library. The OSModelStore.add(id:model:hydrating:) method is calling this dictionary subscript setter, which is causing the crash.

A: Unfortunately, the steps to reproduce this crash are not provided in the crash report. However, we can try to reproduce the crash by calling the OSModelStore.add(id:model:hydrating:) method in a controlled environment.

A: The expected behavior of the OSModelStore.add(id:model:hydrating:) method is that it should be called without crashing the app.

A: To fix the crash, we need to investigate further and provide a fix for the OSModelStore.add(id:model:hydrating:) method. This may involve reviewing the implementation of the method, checking for dictionary subscript setter issues, and providing a fix to prevent the crash from occurring.

A: Some possible solutions to fix the crash include:

  1. Review the OSModelStore.add(id:model:hydrating:) method: Review the implementation of the OSModelStore.add(id:model:hydrating:) method to ensure that it is correct and does not cause any crashes.
  2. Check for dictionary subscript setter issues: Check if there are any issues with the dictionary subscript setter in the libswiftCore.dylib library that could be causing the crash.
  3. Provide a fix for the OSModelStore.add(id:model:hydrating:) method: Provide a fix for the OSModelStore.add(id:model:hydrating:) method to prevent the crash from occurring.

A: To update the OneSignal iOS SDK to the latest version, you can follow these steps:

  1. Check the OneSignal website: Check the OneSignal website for the latest version of the iOS SDK.
  2. Download the latest version: Download the latest version of the iOS SDK from the OneSignal website.
  3. Update your project: Update your project to use the latest version of the iOS SDK.

A: Some best practices to prevent crashes like this in the future include:

  1. Review your code: Review your code to ensure that it is correct and does not cause any crashes.
  2. Use debugging tools: Use debugging tools to identify and fix issues in your code.
  3. Test your app: Test your app thoroughly to ensure that it is stable and does not crash.

In conclusion, the crash that occurs when calling OSModelStore.add(id:model:hydrating:) in the OneSignal iOS SDK is a complex issue that requires further investigation. By following the steps outlined in this article, you can help prevent crashes like this in the future and ensure that your app is stable and reliable.