Fix for issue 1605 #2133
Closed
Fix for issue 1605 #2133
+6
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…on is found, throw error 209.
Fix for issue #1605. If a session token is set but no matching _Sessi…
ghost
added
the
|
Supersed by #2154 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
According to the guide at https://parse.com/docs/ios/guide#sessions-handling-invalid-session-token-error: "When a device's session token no longer corresponds to a PFSession object on the Parse Cloud, all API requests from that device will fail with 'Error 209: invalid session token'."
However, with the current implementation no error is thrown as expected. Issue 1605 describes this as well. This pull request will throw error 209 if a session token is set but no matching _Session is found.