Remove the hardcoding of the JWT calls + switch to session fetcher fo… #9
Conversation
This file contains 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
…r the remote call Now that we have fixed the generic JWT auth, we can switch to actually using it. But after we did that, we found that actual remote call was also not working although we did use NSURLConnection. Tried switching that to GTMSessionFetcher as well and it worked!! It is not using a background session since the input is still a data object and not a file. Must be something to do with the thread or queue being used, since I was using the main queue before.
shankari
added a commit
that referenced
this pull request
Mar 5, 2016
Remove the hardcoding of the JWT calls + switch to session fetcher fo…
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.
…r the remote call
Now that we have fixed the generic JWT auth, we can switch to actually using
it. But after we did that, we found that actual remote call was also not
working although we did use NSURLConnection. Tried switching that to
GTMSessionFetcher as well and it worked!!
It is not using a background session since the input is still a data object and
not a file. Must be something to do with the thread or queue being used, since
I was using the main queue before.