I took apple’s sample code tweeting and modified it so that it doesn’t use

Question

0

Asked: May 30, 20262026-05-30T09:30:34+00:00 2026-05-30T09:30:34+00:00

I took apple’s sample code tweeting and modified it so that it doesn’t use

0

I took apple’s sample code “tweeting” and modified it so that it doesn’t use ARC (download my project here to test the problem yourself). Actually only one “autorelease” statement was needed:

// Set up the built-in twitter composition view controller.
tweetViewController = [[[TWTweetComposeViewController alloc] init]autorelease];

// Set the initial tweet text. See the framework for additional properties that can be set.
[tweetViewController setInitialText:@"Hello. This is a tweet."];

// Create the completion handler block.
[tweetViewController setCompletionHandler:^(TWTweetComposeViewControllerResult result) {
    NSString *output;

    switch (result) {
        case TWTweetComposeViewControllerResultCancelled:
            // The cancel button was tapped.
            output = @"Tweet cancelled.";
            break;
        case TWTweetComposeViewControllerResultDone:
            // The tweet was sent.
            output = @"Tweet done.";
            break;
        default:
            break;
    }

    //[self performSelectorOnMainThread:@selector(displayText:) withObject:output waitUntilDone:NO];

    // Dismiss the tweet composition view controller.
    [self dismissModalViewControllerAnimated:NO];


}];

// Present the tweet composition view controller modally.
[self presentModalViewController:tweetViewController animated:YES];

If you send the tweet or click cancel in “tweetViewController” you would expect that the tweetViewController is deallocated. Instead the object remains in memory including the attached image (if you have attached one in the tweet) . So, if the user tries to make another tweet the app’s memory grows bigger because tweetViewController leaked.

As you notice, tweetViewController isn’t mentioned inside the block so it isn’t automatically retained..

I used instruments and proved 1 that “[[TWTweetComposeViewController alloc] init]” causes a memory leak.

Another thing I tried in order to prove it, was to ” NSLog(“%@”,tweetViewController); ” a few runcycles after the controller has been dismissed. Normally the program should have crashed because tweetViewController would not be pointing to a TWTweetComposeViewController instance. Instead it printed correctly the previous instance, proving the memory leak.

The only way I have found in order to avoid this is by violating the memory management rules and is the following:

[tweetViewController setCompletionHandler:^(TWTweetComposeViewControllerResult result) {

    // Dismiss the tweet composition view controller using animated YES!!
    [self dismissModalViewControllerAnimated:YES];
    [tweetViewController release];

}];

If you dismiss it without animation, a memory leak occurs… Have you noticed the problem? Am I doing something wrong? Try it yourself and comment please…
instruments showing the "leak"