"Invalid Input Data Please Verify Unique Constraints " after migrating from OneClick to AWS

[NOR-TB]

Bug report

Describe the bug

Moved my strapi build from digitaloceans one click service to aws self-installed strapi on ubuntu 18. with postgres rds.

Database was migrated using aws datamigration service. Content was successfully migrated. There were some initial errors, but repeat of the process with truncate enabled allowed the database to be moved successfully.

Strapi is showing the data, but when trying to edit the migrated content you get met with the error "Invalid Input Data Please Verify Unique Constraints ".

Steps to reproduce the behaviour

1. Open a digitalocean one click strapi app add some content.
2. Set up aws strapi server and database and s3 bucket and steps.
3. move database from digitalocean to aws.
4. try to change content after logging in.

Expected behavior

No error and successful edit of the fields.

System

• Node.js version: 10.19.0
• NPM version: 6.14.4
• Strapi version: 3.46
• Server: AWS EC2 Ubuntu 18
• Database: postgres on aws rds
• Operating system: windows os

Additional context

from the backside the postgres database is giving a 400 error. But if i were to add a item to the collection content, then that item works fine. I just cant edit or change SOME fields in the cms for content that was migrated over.

Ive tried with node_env to both dev and production.

ive tried strapi development mode.

ive tried strapi production.

ive tried updating all the npm packages and updating to latest strapi build.

still getting the same error.

is this issue related to security groups on aws? or the s3 bucket for file uploads?

any help is appreciated.

[derrickmehaffy]

This is a templated message

Hello, please follow the issue template.

A proper issue submission let's us better understand the origin of your bug and therefore help you.

I will reopen your issue when we receive the issue following the template guidelines and properly fill out the template. You can see the template guidelines for bug reports here.

Please update the issue with the template and we can reopen this report.

Thank you.

[NOR-TB]

This is a templated message

Hello, please follow the issue template.

A proper issue submission let's us better understand the origin of your bug and therefore help you.

I will reopen your issue when we receive the issue following the template guidelines and properly fill out the template. You can see the template guidelines for bug reports here.

Please update the issue with the template and we can reopen this report.

Thank you.

fixed

[derrickmehaffy]

@Tej-Bains

Strapi version: 3.46

We issued a release in v3.5.0 last week that should address this, can you try updating and see if that fixes your issue?

[mrmadhat]

I was getting this error because of a mismatch in package versions. During my deploy I switched the upload provider from strapi-provider-upload-aws-s3 to strapi-provider-upload-cloudinary but when I installed the new provider I didn't realise that the installed version of the upload provider was 3.5.1 and strapi (and other strapi related packages) was 3.4.6. Making sure the provider version matched the strapi version fixed the issue for me.

[brnpimentel]

I updated to last version 3.5.x and fixed the issue

[derrickmehaffy]

Marking as closed as two confirmations stated it's fixed.

[gramsco]

I have the same issue with 3.6.1.
My hypothesis is that bugs like in Strapi that occur when:

• you add a field to a collection
• you add data to the field for an object in said collection
• you remove the field

because Strapi does not remove the data associated to the field. Which could be a good opt-in by the way: "do you want to remove the data associated to the field you're deleting?"

I will try to go directly into the DB to fix the issue (and update my post)