[Bug]: -[OSObservable notifyChange:] Crash

[Vatsal4GVM]

What happened?

iOS app crashed in production with a stack trace showing OneSignal frames.

Steps to reproduce?

No idea. This is a remote crash report from Crashlytics.

What did you expect to happen?

The library should not cause a crash, regardless of what I may be doing wrong in using it.

OneSignal iOS SDK version

Release 3.12.9

iOS version

16

Specific iOS version

* iOS 16.0

Relevant log output

Crashed: com.apple.usernotifications.UNUserNotificationServiceConnection.call-out
0  libobjc.A.dylib                0x2e18 objc_retain + 8
1  libobjc.A.dylib                0x2e18 objc_retain_x0 + 8
2  OneSignal                      0x32714 -[OSObservable notifyChange:] + 72
3  OneSignal                      0x23c6c -[OSPermissionState setAnsweredPrompt:] + 80
4  OneSignal                      0x20aa0 __69-[OneSignalNotificationSettingsIOS10 getNotificationPermissionState:]_block_invoke_2 + 100
5  OneSignal                      0x25e38 __91-[OneSignalUNUserNotificationCenter onesignalGetNotificationSettingsWithCompletionHandler:]_block_invoke + 60
6  libdispatch.dylib              0x24b4 _dispatch_call_block_and_release + 32
7  libdispatch.dylib              0x3fdc _dispatch_client_callout + 20
8  libdispatch.dylib              0xb694 _dispatch_lane_serial_drain + 672
9  libdispatch.dylib              0xc214 _dispatch_lane_invoke + 436
10 libdispatch.dylib              0x16e10 _dispatch_workloop_worker_thread + 652
11 libsystem_pthread.dylib        0xdf8 _pthread_wqthread + 288
12 libsystem_pthread.dylib        0xb98 start_wqthread + 8

Code of Conduct

• I agree to follow this project's Code of Conduct

[nan-li]

Hi @Vatsal4GVM thanks for reporting this, we will investigate.