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.

Sign up for GitHub

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

Jump to bottom

No useful results when app crashes. #3

Closed
ob opened this issue Jan 13, 2017 · 1 comment
Closed

No useful results when app crashes. #3

ob opened this issue Jan 13, 2017 · 1 comment
Assignees
@ob
Labels
bug

Comments

@ob
Copy link
Member

ob commented Jan 13, 2017

Bluepill handles the case when a test crashes. However, if the app itself crashes on launch, the console gets a useless message like this:

[ CRASH  ] (1) (null)/(null) crashed app.

And nothing useful is reported in the output report. Bluepill should have a special way of logging and reporting an app crashing on launch.
@oliverhu oliverhu added the bug label Jan 13, 2017
@ob ob mentioned this issue Jan 14, 2017
Closed
@ob
Copy link
Member Author

ob commented Feb 7, 2017

Fixed by #49

@ob ob closed this as completed Feb 7, 2017
RainNapper pushed a commit to RainNapper/bluepill that referenced this issue Jun 16, 2021
@CrabDude @jparise
Add PrettierLinter (MobileNativeFoundation#3)
7e482b8
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ob ob

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ob @oliverhu