Saving an image with ParseFile

[jaysonng]

I'm trying to save a UIImage to a ParseFile via cloudcode. I've gotten it to encode and decode using data.base64encodedstring() but I always get this error when saving on Parse-swift-server.

Error Creating New LokalityImage: ParseError code=130 error=Invalid file upload.

I was wondering could this be because I'm trying to a UIImage as the data: of ParseFile(name:,data:) ? As I think Vapor doesn't support it somehow?

I can't pinpoint or get more data aside from the error stemming from trying to save ParseFile over at Parse-swift-server.

When I save directly using Parse-Swift sdk, it works fine.

thanks!

[jaysonng]

Come to think of it, the data I'm sending over isn't a UIImage but a jpeg from the said UIImage. So I may be off thinking that's the problem.

Any idea what I should look into on why I can't save on Parse-Swift-Server?

[jaysonng]

Saving works fine if I use Javascript Cloud Code, so all I can think of is that its a setting in Parse-Server-Swift that's causing me to get this an error.

[jaysonng]

And do you think it has something to do with these lines in Parse-Server? I think this is where the error comes from when I save via Parse-Server-Swift.

    if (!req.body || !req.body.length) {
      next(new Parse.Error(Parse.Error.FILE_SAVE_ERROR, 'Invalid file upload.'));
      return;
    }

https://github.com/parse-community/parse-server/blob/91dde99d3dba55d2db24221c4ab867db2f82126e/src/Routers/FilesRouter.js#L132-L135

Do we not have a req.body when I save a ParseFile in Parse-Swift-Server?

[jaysonng]

If it helps... the req.body when using JS CloudCode

body: <Buffer 2f 39 6a 2f 34 41 41 51 53 6b 5a 4a 52 67 41 42 41 51 41 41 53 41 42 49 41 41 44 2f 34 51 43 4d 52 58 68 70 5a 67 41 41 54 55 30 41 4b 67 41 41 41 41 ... 112802 more bytes>

vs when using Parse-Swift-Server

body: {
 '/9j/4AAQSkZJRgABAQAASABIAAD/4Q < ... truncated ... > 2Q': '=' 
},

[jaysonng]

I think I fixed it with a combination of my Parse-Server settings and iOS app changes.

in short, Parse-Swift-Server problem this is not.