Skip to content
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]: Crashes when used in a default rails/puma server on macOS #32

Open
1 task done
bmulholland opened this issue Aug 22, 2023 · 1 comment
Open
1 task done
Labels

Comments

@bmulholland
Copy link

What happened?

When trying to send a notification, I get this:

objc[65540]: +[__NSCFConstantString initialize] may have been in progress in another thread when fork() was called.
objc[65540]: +[__NSCFConstantString initialize] may have been in progress in another thread when fork() was called. We cannot safely call it or ignore it in the fork() child process. Crashing instead. Set a breakpoint on objc_initializeAfterForkError to debug.

And no notifications are delivered

Steps to reproduce?

Trigger a notification from within puma, I guess

Root cause is:
https://github.com/typhoeus/typhoeus/issues/687
and
https://github.com/typhoeus/ethon/issues/206

But these are longstanding open issues. Perhaps Onesignal should reconsider using a library with a longstanding crash?

What did you expect to happen?

obvious

Relevant log output

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@dzirtusss
Copy link

Agree 200% 🙏 please consider using some http lib w/o libcurl native extensions. Unfortunatelly they are all prone to crashing with ruby libs - ethon, curb, practically for many years.

🙏 default net::http should be good-enough as a gem dependency, thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants