overrides for Autocomplete component in amplify studio-generated form not working

[floriankrueper]

Before opening, please confirm:

• I have searched for duplicate or closed issues.
• I have read the guide for submitting bug reports.
• I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
• I have removed any sensitive information from my code snippets and submission.

App Id

d20x6uoo2bidyv

Region

eu-central-1

Environment name

develop

Figma File Version (if applicable)

No response

Amplify CLI Version

12.4.0

If applicable, what version of Node.js are you using?

No response

What operating system are you using?

No response

Browser type?

No response

Describe the bug

I created a form with amplify studio.
In that form i use a relation to another model, which is why an Autocomplete component is included in the form.
However, the Autocomplete component gets wrapped in an ArrayField by Amplify Studio.
While the Autocomplete component has set hideLabel=true, the outer ArrayField is responsible for rendering the label for the construct.
The problem now is, that we cannot override the label for the ArrayField. ArrayField simply misses the line:
{...getOverrideProps(overrides, "FIELDNAME")}

Expected behavior

Something like
{...getOverrideProps(overrides, "FIELDNAME_container")}
should be included in the outer ArrayField, so we can properly access the label of an Autocomplete Component.

Reproduction steps

1. Create a graphql schema with two Models with a relation
2. Create a form using Amplify Studio
3. Import that form into your REACT project
4. Try to override the label for the resulting Autocomplete field

Project Identifier

No response

Additional information

As a workaround, i simply put
{...getOverrideProps(overrides, "FIELDNAME_container")}
in the auto-generated form and am now able to access the label and translate it.

[ykethan]

Hey @floriankrueper, thank you for reaching out. On discussing with the team, I was able to confirm the behaviour. Glad to hear that you have a workaround for this.
marking this as bug.