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

exception Signal 5, Code 0 #456

Closed
2 of 5 tasks
peacechen opened this issue Aug 3, 2018 · 5 comments
Closed
2 of 5 tasks

exception Signal 5, Code 0 #456

peacechen opened this issue Aug 3, 2018 · 5 comments
Assignees

Comments

@peacechen
Copy link

peacechen commented Aug 3, 2018

OS:

  • Windows
  • MacOS
  • Linux

Platform:

  • iOS
  • Android

Output of node -v && npm -v && npm ls --prod --depth=0

v9.3.0
5.5.1

Config:

Sentry.config('🔑').install();

I have following issue:

My app reported the exception exception Signal 5, Code 0. The stack trace shows a code push check happened at 03:00, then 12 hours later it reported the exception. What is this error? I searched but couldn't find anything on it.

console [CodePush] An update is available but it is not targeting the binary version of your app. 03:00:01
console [CodePush] App is up to date. 03:00:01
exception Signal 5, Code 0 15:43:10

Steps to reproduce:
Unknown

Actual result:
Exception report

Expected result:
No exception

@sentry-probot
Copy link

sentry-probot bot commented Aug 3, 2018

Hi there, I just edited this for you. Try not to post your DSN on GitHub.

@HazAT
Copy link
Member

HazAT commented Aug 7, 2018

Can you link me to the event in your sentry.io account?

@HazAT HazAT self-assigned this Aug 7, 2018
@peacechen
Copy link
Author

@HazAT
Copy link
Member

HazAT commented Aug 8, 2018

Thanks for the link.
So I think there is nothing we can do here, I think it's probably iOS closing the app in background due to memory, reboot, os update or anything.
Signal 5 if I am correct means # Input/output error can be anything.
Do other crashes show up normally?

@peacechen
Copy link
Author

Other errors do show up correctly. This was an oddball event that I have no other insight into and am trying to determine if a fix is needed. Thanks for looking into this.

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

No branches or pull requests

2 participants