Skip to content

Getting WebException instead of ParseException for InvalidSessionToken #99

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

Closed
rehos opened this issue Nov 24, 2015 · 4 comments
Closed
Milestone

Comments

@rehos
Copy link

rehos commented Nov 24, 2015

Parse .NET SDK 1.6.2 within Xamarin iOS and Xamarin Android apps.

If the session of a user has been revoked (either by removing the session manually from the Session table or if user changed password on other device), the SDK now generates a WebException with status ProtocolError instead of a ParseException with code InvalidSessionToken.

Note: I can see the correct JSON with the correct parse error code is being returned from the Parse backend with HTTP status code 400.

@richardjrossiii
Copy link
Contributor

That may have happened when we refactored HttpClient. I'll look into it. Thanks for the report!

@rehos
Copy link
Author

rehos commented Nov 28, 2015

I also noticed that a script error results in a WebException with status ProtocolError instead of a ParseException with code ScriptFailed.

@brett-estabrook
Copy link

I'm seeing a similar problem, whats the latest version I should downgrade to and see this fixed (or when is a fix coming out).

http://stackoverflow.com/questions/34340677/parseexceptions-not-getting-thrown-for-callfunctionasync

@hallucinogen hallucinogen added this to the 1.7.0 milestone Dec 17, 2015
@hallucinogen
Copy link
Contributor

This should be fixed in #132. Feel free to reopen if the problem persists

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

4 participants