-
Notifications
You must be signed in to change notification settings - Fork 264
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
[Bug]: Main thread is getting blocked during initialisation #1452
Comments
I'm seeing the same thing ... launch time is really slow after adding the OneSignal SDK for iOS. |
+1 |
+1 This crash happened during an app review and caused us to get rejected. Any workarounds?? |
+1 crashed on app review and was rejected. |
seems like we have the same crash Thread 0 name: Dispatch queue: com.apple.usernotifications.UNUserNotificationServiceConnection |
And once again, we have the same crash from app review team: Thread 0 name: Dispatch queue: com.apple.usernotifications.UNUserNotificationServiceConnection |
What happened?
The app's main thread hanged for more than 3 seconds due to usage of synchronous deprecated API applicationIconBadgeNumber.
Steps to reproduce?
What did you expect to happen?
The app's main thread is not blocked during OneSignal initialisation.
OneSignal iOS SDK version
Release 5.2.1
iOS version
17
Specific iOS version
Relevant log output
Code of Conduct
The text was updated successfully, but these errors were encountered: