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

AFNetworking error does not trickle all the way back through the callbacks. #11

Open
spilliams opened this issue Aug 21, 2014 · 0 comments

Comments

@spilliams
Copy link

(I'm using NRGramKit 1.4)
My app makes a call to log in, and AFNetworking (1.3.4) comes back with an error. The error trickles up to NRGramKit.m:219, where the error data is no longer used in the callback chain. Following the chain from there, we pass through NRGramKit.m:145 (which gets nil parameters as well) before hitting NRGramKit.m:241, where an IGUser is created using the nil dictionary.

By the time the callback chain makes it back to the original call to +loginInWebView:loginLoadingCallback:finishedCallback: we have lost track of the fact that there was an error, and instead we have an empty user object.

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

1 participant