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
Correct useage ? #97
Comments
This code seems correct to me. I can't get why there would be a leak here. |
Thanks for the speedy reply , it is puzzling me as a new view added with just above in viewDidLoad leaks , and logs the dealloc fine without it ? It only leaks on verifyCredentials , the self.twitter = [STTwitterAPI twitterAPIAppOnlyWithConsumerKey:kTwitterAPI consumerSecret:kTwitterSECRET]; is fine Any thoughts to where it could be leaking ? |
Could you check this method please ?
|
In STTwitterAPI.m, could you replace the implementation of
|
Sorry still the same issue |
Also can you change this?
|
Sorry no , still no dealloc logging |
OK could you please send me a minimal project demonstrating the issue? and I'll have a look tonight. nicolas at seriot dot ch |
Yes I will send it over , thanks for your time ! |
I closed this as the issue was my 'weakSelf' call in the block causing this |
Is this the correct useage to verify my own app ?
it is all working correctly but the view this is in does not dealloc while this code is run
My project is ARC but I always log out the dealloc method to see if it is cleaning up ok
If I enter / exit this view with just the code below the memory keeps increasing
//
self.twitter = [STTwitterAPI twitterAPIAppOnlyWithConsumerKey:kTwitterAPI consumerSecret:kTwitterSECRET];
[_twitter verifyCredentialsWithSuccessBlock:^(NSString *bearerToken) {
NSLog(@"Access granted with %@", bearerToken);
} errorBlock:^(NSError *error) {
NSLog(@"-- error %@", error);
}];
The text was updated successfully, but these errors were encountered: