Skip to content

The failure message should have the response in a byte array. #284

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

Merged
merged 1 commit into from
Aug 9, 2013

Conversation

fixedd
Copy link
Contributor

@fixedd fixedd commented Aug 9, 2013

handleSuccessMessage() was being (properly) handed a byte array, but handleFailureMessage() was being passed a string. This adjusts the call to handleFailureMessage() to pass a byte array as well.

handleSuccessMessage() was being (properly) handed a byte array, but handleFailureMessage() was being passed a string. This adjusts the call to handleFailureMessage() to pass a byte array as well.
loopj added a commit that referenced this pull request Aug 9, 2013
The failure message should have the response in a byte array.
@loopj loopj merged commit 832812c into android-async-http:master Aug 9, 2013
@intrications
Copy link

Doesn't this revert a change made in #198 in order to fix a crash?

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

Successfully merging this pull request may close these issues.

3 participants