ParseFile save fails on parser-server after migration: Unable to encode an unsaved ParseFile

[smanikandan14]

I am using parse-android SDK 1.13.0. I am able to upload file to parse's backend.

But when i change my server endpoint to migrated end point, upload fails.

{
    "code": 130,
    "error": "Invalid file upload."
}

I added console logs in file.js on parse-server i found the request.body is empty.

Files.js processCreate req: [object Object] : {} : undefined

var processCreate = function(req, res, next) {
console.log(" Files.js processCreate req:"+req+" : "+ JSON.stringify(req.body)+" : "+req.body.length
if (!req.body || !req.body.length) {
    next(new Parse.Error(Parse.Error.FILE_SAVE_ERROR,
         'Invalid file upload.'));
    return;
  }

Exception message shown on client side.

iIllegalStateException: Unable to encode an unsaved ParseFile

Seems to be an issue on the parse-server side. The request body is found empty. I reported this issue on parse-android-sdk. Since the sdk could upload to parse hosted backend. Suspect is on the parse-server side.

[smanikandan14]

Reported the same on parse-android-sdk. parse-community/Parse-SDK-Android#384

[smanikandan14]

@gfosco Sorry, just checking if this is a valid bug. I couldn't upload images to parse-server after migration. Any solutions appreciated.

[gfosco]

Will look at this within the next day or two, looks valid, will combine other issues to point here.

[jpmassena]

@smanikandan14, are you using OkHttp dependency on you app?

As soon as I added OkHttp, I started to have some problems with my parse-server:

• First all requests to parse-server crashed the app. The cause was that I was receiving or sending null Headers (parse-x-client-key or something similar) and ParseOkHttpClient (from the SDK) crashed.
• I added the clientKey to the app/server and that problem went away, but now I'm getting the same error as you do. I removed the OkHttp dependency and I'm able to upload files again.

So, the issue seems to be around the SDK, at least for me as I only have problems when using OkHttp dependency on my app.

[Spacelapp]

Got the same error after migration: [Error]: Invalid file upload. (Code: 130, Version: 1.12.0)
Any news on this @gfosco ?

[JoshR604]

I am using the .NET sdk and I get this error as well 'Invalid file upload' but I suspect the bug might be in the SDK as I can upload text files and images directly to my parse-server using cURL.

[JoshR604]

I have found a solution to my issue by explicitly setting the MIME type when uploading a ParseFile.

[flovilmart]

@gfosco idea on that, is that because we use a raw body parser and the content maybe encoded in another format depending on the client configuration (usually multipart/form-data with boundaries)

[oyvindvol]

I am using the .NET SDK to upload PFFiles (images), and also got the invalid file upload message. After setting MIME type explicitly in the PFFile like @JoshR604 said, I get this exception instead: Exception of type 'Parse.ParseException' was thrown. with no inner exception message.

When I change back to my old Parse.com-hosted server, it works fine.

[oyvindvol]

@JoshR604 Are you setting the MIME type in the ParseFile constructor? new ParseFile("filename", data, 'image/png'); ?

[JoshR604]

@oyvindvol Yes, here is the code I am using:

var file = new ParseFile ("photo.jpg", data, "image/jpeg");
await file.SaveAsync ();
parseUser.Add ("photo", file);
await parseUser.SaveAsync ();

Also, I am using the .NET sdk on Xamarin and have tested this code on iOS and Android.

[perriera]

I just discovered today that by default the migration feature of the new Parse dashboard only migrates your data. It does not migrate the contents of the ParseFile object itself. In my case I am storing jpg and png images inside a ParseFile. When I did the first mirgration the ParseFile objects migrated but they pointed towards the www.parsefss.com url. In my case I was able to by pass the need for the migration tool because I happened to have a backup/restore feature on my client's website. Where I was able to do a full backup while still on the Parse.com database. Then when I switched to my open source Parse Server with it's own MongoDB, I did a full restore. This caused the file uploading to store a brand new copy of the ParseFile images inside the MongoDB database. I was able to check this simply by doing a View Image with the browser.

So it looks like all you have to do is something similar to this and you're ready to go!

I did a double check on my website before posting this comment. The open source Parse Server uploads, edits and deletes images just fine!