Need to run code on save and log from Parse Cloud Code when updating PFObject's key in iOS app

Question

I have a PFObject that has an array key. I can successfully call addObject: on this PFObject, and can confirm that the object has been added to the array key properly using an NSLog. However, when I try to save the PFObject to Parse, even though it says everything went successful, the changes are not shown in the Data Browser.

I have tried everything, and can even get this to work in an older version of my app, but for some reason it will not work anymore.

I posted another StackOverflow question about this here

The only response I got were some comments saying that I should trigger a "before save" function and log everything via Cloud Code. The problem is I don't know javascript, and I've been messing around with Cloud Code and nothing's happening.

Here is the code I am executing in my app:

[self.message addObject:currentUsersObjectId forKey:@"myArrayKey"];

And then I am using saveInBackgroundWithBlock:

I need to alter Cloud Code so that it will check the self.message object's "myArrayKey" before saving and log the results.

Edit 2:

Here is how I create currentUsersObjectId:

NSString *currentUsersObjectId = [[NSString alloc]init];

PFUser *user = [PFUser currentUser];

currentUsersObjectId = user.objectId;

Edit 3:

Here is the save block

[self.message saveInBackgroundWithBlock:^(BOOL succeeded, NSError *error) {
    if (error) {
        NSLog(@"An error has occurred.");
    } 
}];

Edit 4:

After adding Timothy's cloud code, the saveInBackgroundWithBlock: now does not successfully complete. Instead an error occurs, and the error object NSLogs as `"Error: Uncaught Tried to save an object with a pointer to a new, unsaved object. (Code: 141, Version: 1.2.17)" and also as:

Error Domain=Parse Code=141 "The operation couldn’t be completed. (Parse error 141.)" UserInfo=0x15dc4550 {code=141, error=Uncaught Tried to save an object with a pointer to a new, unsaved object.} {
    code = 141;
    error = "Uncaught Tried to save an object with a pointer to a new, unsaved object.";
}

Here is my complete Cloud Code file after adding Timothy's code:

Parse.Cloud.define('editUser', function(request, response) {
    var userId = request.params.userId;
        //newColText = request.params.newColText;

    var User = Parse.Object.extend('_User'),
        user = new User({ objectId: userId });

    var currentUser = request.user;

    var relation = user.relation("friendsRelation");
    relation.add(currentUser);

    Parse.Cloud.useMasterKey();
    user.save().then(function(user) {
        response.success(user);
    }, function(error) {
        response.error(error)
    });
});

Parse.Cloud.beforeSave("Messages", function(request, response) {
    var message = request.object;

    // output just the ID so we can check it in the Data Browser
    console.log("Saving message with ID:", message.id);
    // output the whole object so we can see all the details including "didRespond"
    console.log(message);

    response.success();
});

// log the after-save too, to confirm it was saved
Parse.Cloud.afterSave("Messages", function(request, response) {
    var message = request.object;

    // output just the ID so we can check it in the Data Browser
    console.log("Saved message with ID:", message.id);
    // output the whole object so we can see all the details including "didRespond"
    console.log(message);

    response.success();
});

Please show your full code that saves, the logging comments on your other question were suggestions to help you debug the issue. Also please give details of the column types (is myArrayKey of type Array<string> or Array<_User> etc). — Timothy Walters
Need to see your iOS code (from where you get currentUsersObjectId to your save block), you can remove that Cloud Code from your question as it is completely unrelated. — Timothy Walters
.. and the full save block? So far everything looks fine (as long as there is a current user). Consider placing NSLog statements everywhere to confirm that everything is as expected (user, currentUsersOjbectId, self.message, success/error code etc). — Timothy Walters
I just added the save block. I have already NSLogged everything. Succeeded comes back as true, no error, everything NSLogs. Even before saving, if I NSLog self.message it shows the value added to the key. It makes no sense. — user3344977

Timothy Walters Timothy Walters · Accepted Answer · 2014-07-15T08:03:06

After much back and forth, I'm stumped as to why this isn't working for you. As for logging in Cloud Code, if you follow the guide on adding code you can add the following to your main.js and deploy it:

Parse.Cloud.beforeSave("Messages", function(request, response) {
    var message = request.object;

    // output just the ID so we can check it in the Data Browser
    console.log("Saving message with ID:", message.id);
    // output the whole object so we can see all the details including "didRespond"
    console.log(message);

    response.success();
});

// log the after-save too, to confirm it was saved
Parse.Cloud.afterSave("Messages", function(request, response) {
    var message = request.object;

    // output just the ID so we can check it in the Data Browser
    console.log("Saved message with ID:", message.id);
    // output the whole object so we can see all the details including "didRespond"
    console.log(message);

    response.success();
});

With those in place you have plenty of server-side logging that you can check.

Need to run code on save and log from Parse Cloud Code when updating PFObject's key in iOS app

2 Answers