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

Jump to bottom

Non-ASCII Characters Breaks OCUnitReportParser #34

Closed
blakewatters opened this issue Apr 9, 2012 · 0 comments · Fixed by #35
Closed

Non-ASCII Characters Breaks OCUnitReportParser #34

blakewatters opened this issue Apr 9, 2012 · 0 comments · Fixed by #35

Comments

@blakewatters
Copy link
Contributor

My test suite generates a number of NSError objects in tests without an NSLocalizedDescriptionKey configured for the userInfo of the NSError instance, which results in a default error message of "The operation couldn’t be completed. (Test error 0.)". The apostrophe within the text causes an exception to be raised during parsing:

#<ArgumentError: invalid byte sequence in US-ASCII>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix for ArgumentError when processing log messages containing UTF-8 data... GateGuru/xcoder
2 participants
@blakewatters @rayh