[Bug]: ERROR STATUS 422

[Tindavetran10]

Version

• [X] Yes

General Question

• [X] No

What happened?

I have finished the "npm run upload_metadata" step and moved to the "npm run upload_metadata" step. And then, the Terminal keeps saying: "There is an issue with the metadata upload. Please check the /build/_ipfsMetasGeneric/_ipfsMetasResponse.json file for more information. Running "npm run upload_metadata" may fix this issue. CATCH ERROR: ERROR STATUS: 422"

I have tried to redo it many times but it doesn't work.

What have you tried?

I Googled and asked the community in the discord server but could not find a solution.

Relevant log output

PowerShell 7.3.0-preview.3
PS D:\minter-dapp> cd backend
PS D:\minter-dapp\backend> npm run deploy_contract

> minter-dapp-backend@0.0.2 deploy_contract
> node utils/nftport/deployContract

Is all REQUIRED contract information correct in config.js? (y/n): y
There is an issue with the metadata upload. Please check the /build/_ipfsMetasGeneric/_ipfsMetasResponse.json file for more information. Running "npm run upload_metadata" may fix this issue.
CATCH ERROR: ERROR STATUS: 422
PS D:\minter-dapp\backend>  npm run deploy_contract

> minter-dapp-backend@0.0.2 deploy_contract
> node utils/nftport/deployContract

Is all REQUIRED contract information correct in config.js? (y/n): y
There is an issue with the metadata upload. Please check the /build/_ipfsMetasGeneric/_ipfsMetasResponse.json file for more information. Running "npm run upload_metadata" may fix this issue.
CATCH ERROR: ERROR STATUS: 422
PS D:\minter-dapp\backend> npm run deploy_contract

> minter-dapp-backend@0.0.2 deploy_contract
> node utils/nftport/deployContract

Is all REQUIRED contract information correct in config.js? (y/n): y
There is an issue with the metadata upload. Please check the /build/_ipfsMetasGeneric/_ipfsMetasResponse.json file for more information. Running "npm run upload_metadata" may fix this issue.
CATCH ERROR: ERROR STATUS: 422
PS D:\minter-dapp\backend> npm run deploy_contract

> minter-dapp-backend@0.0.2 deploy_contract
> node utils/nftport/deployContract

Is all REQUIRED contract information correct in config.js? (y/n): y
There is an issue with the metadata upload. Please check the /build/_ipfsMetasGeneric/_ipfsMetasResponse.json file for more information. Running "npm run upload_metadata" may fix this issue.
CATCH ERROR: ERROR STATUS: 422
PS D:\minter-dapp\backend> npm run upload_metadata

> minter-dapp-backend@0.0.2 upload_metadata
> node utils/nftport/uploadMetas

ontract

> minter-dapp-backend@0.0.2 deploy_contract
> node utils/nftport/deployContract

Is all REQUIRED contract information correct in config.js? (y/n): y
There is an issue with the metadata upload. Please check the /build/_ipfsMetasGeneric/_ipfsMetasResponse.json file for more information. Running "npm run upload_metadata" may fix this issue.CATCH ERROR: ERROR STATUS: 422
PS D:\minter-dapp\backend>

Protect your information

• [X] I Agree

[Kornoto3434]

I have the same issue with deploying the contract, 422 Catch error, at first it deployed while i was using version 0.01 but then i lost the config.js file when i ws supposed to update contract then i started from scratch using the new version. its worse. so many errors. Well, try going to C:\Users\pc\AppData\Local then delete log files anbd try again. but the metadata problem, download version 0.01 and only (only) extract and replace the NFTport files. that should help. But i am also having trouble with Catch error 422, when i am suposed to deploy.

[Kornoto3434]

hi, wallet address spacing thats the cause

[neotavi]

A 422 status code occurs when a request is well-formed, however, due to semantic errors it is unable to be processed. I had the wrong date.

[tatoosa]

the date is a future date? thanx

[tatoosa]

solved thanx!

[smitJameson55]

C:\Users\Eigenaar\minter-dapp-1\minter-dapp\backend> npm run deploy_contract

minter-dapp-backend@0.1.0 deploy_contract node utils/nftport/deployContract

Is all REQUIRED contract information correct in config.js? (y/n): y CATCH ERROR: ERROR STATUS: 422 what now?