-
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]: OneSignalCore NSKeyedArchiver Crash #1366
Comments
Note to self: this stack trace is very obscured. But the stack trace looks similar to #1365
|
Hi @danhalliday thanks again for reporting all of these crashes and stack traces. |
@nan-li Thank you for your help. I am still waiting for my release containing 5.1.6 to roll to 100% of my user base so I’ll know more in a week or so. But right now I can say I’m still seeing at least one issue. I have two crashes reported from my new release, here are the traces. iOS 17.4.1 / iPhone 14:
iPadOS 17.4.1 / iPad Air (5th Generation):
|
What happened?
iOS app crashed in production with a stack trace showing OneSignal frames.
Steps to reproduce?
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
5.1.0
iOS version
11 or below
Specific iOS version
* 17.2.1
Relevant log output
Code of Conduct
The text was updated successfully, but these errors were encountered: