jinliu

@jkasten2 The testing unit has some issue related to the matching of any(). Could you assist in getting it operational?

Hello @ayushi-sk, thank you for reporting. It appears that this ANR is caused by a deadlock when accessing SharedPreference upon receiving a notification. Could you please share the complete stack...

@ArsalTech This error is specific to version 5.1.11 and is fixed in 5.1.12. Please update the SDK version to 5.1.12 and let us know if the error still persists. https://github.com/OneSignal/OneSignal-Android-SDK/releases/tag/5.1.12

> We need to delay `OperationModelStore.load()` as well, as this is what does the disk read. See this ANR stack trace: > > ```java > at com.onesignal.common.modeling.Model.initializeFromJson(Model.kt:98) > at com.onesignal.core.internal.operations.impl.OperationModelStore.create(OperationModelStore.kt:68)...

@MichaelOliveiraBx Thank you for reporting this and uploading your work! We are currently reviewing this issue. Out of curiosity, what plans do you have in mind for handling the event...

Hi @ilhomsoliev, in your case, I would recommend using OneSignal.getUser().addObserver to listen for onesignalId when it becomes available. Note that the IDs might not be updated immediately after you log...

@ayushi-sk @gitByEOS Thank you for sharing the valuable info with us! We have released Android SDK 5.1.12 in an attempt to resolve the specific ANR issues. Please give it a...

Hello @CarlBarks, thanks for sharing the stack trace. Could you provide a little more info with any event listener or observer that you have added under OneSignal? From the look...

> @jinliu9508 and OneSignal team. > > We got 18 more crashes in this issue today. An interesting information for you is that 100% of the crashes happen on `Samsung...

@tanveer-noknok A potential fix related to getting a null pointer exception by calling getAppContext has been released in version 5.1.6. Please let us know if the crash still occurs after...