amplify-studio icon indicating copy to clipboard operation
amplify-studio copied to clipboard

Amplify Studio

Open LaymanTeam opened this issue 1 year ago • 2 comments

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.
  • [X] I have removed any sensitive information from my code snippets and submission.

App Id

d2ucdwzh5hzple

Region

us-east-1

Environment name

Layman

Figma File Version (if applicable)

https://www.figma.com/file/6W1gy15JW8BSWcjdJ4W9m5/Layman-Mobile-App-Draft?type=design&node-id=202%3A154&mode=design&t=zDx94cUuJfGx0AJi-1

Amplify CLI Version

NA

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

NA

What operating system are you using?

Windows

Browser type?

Chrome

Describe the bug

Whenever I attempt to fetch the UI from Figma the fetching process just stalls there for hours. A refresh brings up the same stalling process, and moving to any other page just shows an empty UI builder. This is after logging in and out of the UI-Library Settings multiple times, to delete the Figma file, and manually deleting all components as well, even in duplicated environments and duplicate apps. Secondly, when I use the Amplify UI Builder inside Figma, it notes that there are outdated Amplify Components and says it successfully updated them, but there is no change. Similarly, there is no change when I attempt to update the theme through the UI Builder.

Expected behavior

I expected the UI-Builder in Amplify Studio to successfully sync and pull the components I made with Amplify primitives into the space.

Reproduction steps

Screen Shot 2023-06-30 at 4 51 15 PM

  1. Open Amplify Studio (Google Chromium)
  2. Go to "UI-Builder (NEW)"
  3. "UI Library Settings" handle all the above.
  4. "Sync with Figma"
  5. The Syncing process stalls like above, this has been going on each attempt for 48 hours, and doesn't change no matter how long.

Project Identifier

5d22c31ce53acbcfb04e60608c8038ad

Additional information

No response

LaymanTeam avatar Jun 30 '23 21:06 LaymanTeam

I experience the same, is there any update?

asaf242 avatar Jul 14 '23 23:07 asaf242

Hey @LaymanTeam, it appears the Figma sync process does not timeout when trying to import file that has large number of components. I was able to reproduce the issue. Decreasing the number of components and retrying the sync does import the components. Marking this as bug for improvements.

ykethan avatar Jul 19 '23 20:07 ykethan