Collections can't be display.

[Hsin1025]

Before opening, please confirm:

• [X] I have searched for duplicate or closed issues.
• [X] I have read the guide for submitting bug reports.
• [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

App Id

x

Region

us-east-1

Environment name

x

Figma File Version (if applicable)

No response

Amplify CLI Version

10.0.0

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

v18.10.0

What operating system are you using?

Mac

Browser type?

Safari

Describe the bug

I build a collection name Thoughts. But it can't be display on UI. Here is the warning: The components Thoughts were synced with an older version of Amplify Studio. Please re-sync your components with Figma to get latest features and changes.

Expected behavior

The right UI.

Reproduction steps

1. Use item card to build collection.
2. run amplify pull
3. add in index.js

Project Identifier

No response

Additional information

No response

[hein-j]

Hi @Hsin1025 , thanks for raising. We'll start looking into this

[hein-j]

Hi @Hsin1025 , that warning shouldn't interfere with rendering the component (that's a bug on us and we'll fix that). It looks to me like your component is actually rendering, but it's just not grabbing data to display. Can you confirm that you have records saved for the data model that you've selected for your component?

[ykethan]

hey @Hsin1025, following up on this issue. Has the Studio application configured according to the docs here: https://docs.amplify.aws/console/uibuilder/figmatocode/#step-3-configure-your-project

[letsbelopez]

Can you confirm that your collection has items in it? Or if it's connected to a data model, does the data model have any records to display?

If you don't have the correct authorization level for the model, you could get an unauthorized warning in the browser console. Please check for that too.

It looks like the component is generating in your app, ant the warning is a general warning and it doesn't look like it's related with the generated component. I'm going to remove the bug label since this can't be reproduced yet.

[ykethan]

Closing the issue due to inactivity. if you are still experiencing this issue please feel free in tagging us. we would be happy in diving deeper into the issue.