PostMessage validation failed 409 (Conflict)

[tofu00]

I just finished Pt 1 video. but somehow it didn't work.
I'm getting the 409 error whenever i click the submit after choosing the file.

PostMessage validation failed: selectedFile: Cast to string failed for value "{↵ name: 'abcd.PNG',↵ type: 'image/png',↵ size: '24 kB',↵ base64: 'data:image/png;base64,iVBOFXH6UHWZ4XkKeLlsdIh... =',↵ file: {}↵}" (type Object) at path "selectedFile"

[CTZxVULKAN]

I am having the same issue. I even cloned the repo and ran the code stilll the same issue.
It worked on the video though.

[Aman-zishan]

@biswasjishnu @tofu00 I just reached at this bug, the problem was while passing selectedFile from client side it was in object type , we mentioned it to be String in backend.

The solution is to get only the base64 field from frontend data and then POST the request. In order to do that you just have to change the onDone in Forms.js like this.

[CTZxVULKAN]

@Aman-zishan Thanks i will try this out as soon as possible.

[techay-mihir]

@biswasjishnu @tofu00 I just reached at this bug, the problem was while passing selectedFile from client side it was in object type , we mentioned it to be String in backend.

The solution is to get only the base64 field from frontend data and then POST the request. In order to do that you just have to change the onDone in Forms.js like this.

when i use this i got error like file not found what should i do now ?

[CTZxVULKAN]

@techy-mit Could you please be more specific with the issue you are having.
Make sure SelectedFile is defined in your schema
Use this for reference ->

Code in formjs

    <div className={`${classes.root} ${classes.fileInput}`}>
      <FileBase
        type="file"
        multiple={false}
        onDone={(file) => setItemData({...itemData, itemScreenshot: file.base64})} />
    </div>

Code for the schema

import mongoose from 'mongoose';

const itemSchema = mongoose.Schema({
  itemScreenshot: String,
});

const ItemInfo = mongoose.model('ItemInfo', itemSchema);
export default ItemInfo;

Without specific details i cannot help more, you should cross check your actions, reducers, api and the proxy u made in package.json in the client side. The error should lie in one of these places.