-
Notifications
You must be signed in to change notification settings - Fork 129
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
SIGABRT in notifyError #399
Comments
Thanks for the report, @benasher44. I took a look and have some theories. Will report back soon. |
abigailbramble
added
backlog
We hope to fix this feature/bug in the future
scheduled
Work is starting on this feature/bug
and removed
backlog
We hope to fix this feature/bug in the future
labels
Aug 9, 2019
Thank you! |
Found a reproduction case involving calling notify concurrently from a few queues at once. Working on a fix in #401. |
abigailbramble
added
released
This feature/bug fix has been released
and removed
scheduled
Work is starting on this feature/bug
labels
Aug 14, 2019
@benasher44 this is now fixed in https://github.com/bugsnag/bugsnag-cocoa/releases/tag/v5.22.5 |
Great thank you! 🎉 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Issue
We're seeing a SIGABRT inside of Bugsnag in the call to
notifyError:…
.Here's the trace:
Environment
Library versions:
pod -v
): 1.7.2AppDelegate
where Bugsnag is configured?Example code snippet
Here's the ID of the error in the plangrid iOS Bugsnag project :) 5c86619cc74b1f0019fc8ecc. Feel free to go have a look!
The text was updated successfully, but these errors were encountered: