Welcome to the Treehouse Community

The Treehouse Community is a meeting place for developers, designers, and programmers of all backgrounds and skill levels to get support. Collaborate here on code errors or bugs that you need feedback on, or asking for an extra set of eyes on your latest project. Join thousands of Treehouse students and alumni in the community today. (Note: Only Treehouse students can comment or ask questions, but non-students are welcome to browse our conversations.)

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and a supportive community. Start your free trial today.

iOS

Robert Uhler
Robert Uhler
3,637 Points

Challenge Task 3 of 3

Task: "Finally, we need to save these changes up to the Parse back-end. The relation is part of the 'playlist' property, where 'playlist' is an instance of PFObject. Save 'playlist' in the background to save the changes to the relation (don't worry about using any blocks)."

#import "FavoriteMoviesViewController.h"

@implementation FavoriteMoviesViewController

- (void)addVideoToPlaylist:(PFObject *)video {
    // Add custom code below!

    PFRelation *relation = [self.playlist relationforKey: @"videos"];
    [relation addObject: video];
    [self.playlist saveInBackgroundWithBlock:^(BOOL succeeded, NSError *error){ 

    }];
}

@end

Not quite sure why this last task isn't passing.

2 Answers

Stone Preston
Stone Preston
42,016 Points

It says not to worry about blocks. Is there a saveInBackground method you can use possibly that doesn't take a block

Robert Uhler
Robert Uhler
3,637 Points

using [self.playlist saveInBackground] vs saveInBackgroundWithBlock did the trick. I passed a previous task that said to not worry about blocks and leaving the block code blank worked with that particular task , so I thought it should have worked here. Thanks for answers.