When using beforeSave on object with a Pointer column - "error: ParseError code=111 error=schema mismatch for Test.test1; expected Pointer<Test1> but got Object"

[jaysonng]

When using beforeSave trigger on an object that has a pointer to another object like so:

struct Test: ParseObject {

    //: These are required for `ParseObject`.
    var originalData: Data?
    var objectId: String?
    var createdAt: Date?
    var updatedAt: Date?
    var ACL: ParseACL?

    var name: String?
    var test1: Test1?
}

struct Test1: ParseObject {

    //: These are required for `ParseObject`.
    var originalData: Data?
    var objectId: String?
    var createdAt: Date?
    var updatedAt: Date?
    var ACL: ParseACL?

    var description: String?
    var test2: Test2?
    var test3: Test3?
}

Doing nothing but just having the beforeSave trigger on produces a schema mismatch error where it expects a Pointer to the sub-object.

func beforeSaveTest(req: Request) async throws -> HookResponse<Test> {

        if let error: HookResponse<Test> = checkHeaders(req) { return error }
        
        var parseRequest = try req.content.decode(HookTrigObjReq<User, Test>.self)
        let options      = try parseRequest.options(req)
        
        if parseRequest.user != nil {
            parseRequest = try await parseRequest.hydrateUser(options: options, request: req)
        }
        
        guard let object = parseRequest.object else {
            return ParseHookResponse(error: .init(code: .missingObjectId,
                                                  message: "Object not sent in request."))
        }
        
        return HookResponse(success: object)
        
    }

I encountered this as I was trying to save a complex object with multiple pointers and tested with these Test objects getting the same result.

error: ParseError code=111 error=schema mismatch for Test.test1; expected Pointer<Test1> but got Object

[cbaker6]

See my response here: netreconlab/Parse-Swift#151 (comment)

[jaysonng]

See my response here: netreconlab/Parse-Swift#151 (comment)

I think this is a different problem. it wasn't a matter of it having the same schema or anything like that.

I was just passing an already existing object, which has pointed to another object (already existing)

it didn't have to create anything. But passing the object through Parse-Server-Swift BeforeSave causes this error.

i just tested beforeSave on JS cloudcode and it updated fine.

This has something to do with Pointer and XXXXX object and how ParseSwift handles it. I'm just not sure exactly where it goes wrong.

[jaysonng]

As an example. I just tried to update "wohoo" to "wohoo1"

and again got this error:

error: ParseError code=111 error=schema mismatch for Test.test1; expected Pointer<Test1> but got Object

Even when I try it on Dashboard.

[cbaker6]

I don’t see a “beforeSave” trigger in the code you provided. I do see “beforeSaveTest” but that’s not a beforeSave trigger

[jaysonng]

I don’t see a “beforeSave” trigger in the code you provided. I do see “beforeSaveTest” but that’s not a beforeSave trigger

sorry, I call beforeSaveTest using the boot routes builder like so.

    func boot(routes: RoutesBuilder) throws {
        
        let lokalityGroup = routes.grouped("lokality")
        //: Triggers
        lokalityGroup.post("save", "before", object: Lokality.self,
                           trigger: .beforeSave, use: beforeSave)
        lokalityGroup.post("save", "before", object: Test.self,
                           trigger: .beforeSave, use: beforeSaveTest)
   }

with logs

[ INFO ] POST /lokality/save/before [request-id: 2049B8FB-60B5-49E9-AC65-8A80302F75DA]

so it does get called on .save()

[cbaker6]

It still looks like the same problem as #65 (comment) to me. ParseServerSwift uses ParseSwift, the beforeSave webhook is called before an object is created on the server so it will run into the same issue. I think you can improve on your systems design to circumvent this, like not saving empty items for no reason. You should save objects when they actually have data. I gave some examples in the previous links. If you insist on keeping your design, you may need to remove your “beforeSave” code using ParseServerSwift, and us the JS Cloud Code for that part.

You could also never create empty objects on the client, use ParseServerSwift beforeSave to create them if they are nil

[jaysonng]

It's not empty though.

They're already there and existing.

[jaysonng]

See this. The info is already there on the dashboard. I'm just trying to update the row with objectId DrhQdVNrhs

"Wohoo" is a string that's already existing.

The Test1 is existing and pointing to an existing object.

When i try to update "wohoo" to "wohoo1" I get the error.

[jaysonng]

So it's not a matter of creating empty objects this time around but how ParseServerSwift handles saving a Pointer but receiving an object in beforeSave.

Somehow it sees the struct and thinks it's a 'Pointer' but really it's getting a 'Test1' - in beforeSave.

[jaysonng]

I'll give it a try on more of my other classes that have the same setup of pointers a do a beforeSave that already has existing data and see if i get it saving.

The Test classes I use are for posting here on Github but I initially encountered the error on my other classes.

[jaysonng]

I got it to save just now by changing var test1: Test1? on my Test struct by changing it to a Pointer<Test1>? and it saved as expected on ParseDashboard.

The save was just updating an existing object.

struct Test: ParseObject {

    //: These are required for `ParseObject`.
    var originalData: Data?
    var objectId: String?
    var createdAt: Date?
    var updatedAt: Date?
    var ACL: ParseACL?

    var name: String?
    var test1: Test1?
}

to

var test1: Pointer<Test1>?

If that gives you an idea of where we can look?

This "fix" isn't workable as I'd have to toPointer() every time I use the object in my code.

[cbaker6]

I recommend looking at the unit tests and try to create a PR which replicates your scenario. You should be able to do it in the ParseSwift repo as it supports all of the hooks. The test case will most likely go into this file: https://github.com/netreconlab/Parse-Swift/blob/main/Tests/ParseSwiftTests/ParseHookTriggerTests.swift.

[jaysonng]

I recommend looking at the unit tests and try to create a PR which replicates your scenario. You should be able to do it in the ParseSwift repo as it supports all of the hooks. The test case will most likely go into this file: https://github.com/netreconlab/Parse-Swift/blob/main/Tests/ParseSwiftTests/ParseHookTriggerTests.swift.

My coding skills haven't gotten that far yet. 😄 I mean I've done a few. It's how I test the methods. but not sure how to test the hooks yet directly like in that ParseHookTriggerTest.swift. I'll look into it though.

thanks