amplify pull throws FeatureFlags is not initialized error

[ykethan]

Before opening, please confirm:

• I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
• 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.

How did you install the Amplify CLI?

No response

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

No response

Amplify CLI Version

10.4.1

What operating system are you using?

Windows

Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

no

Amplify Categories

Not applicable

Amplify Commands

pull

Describe the bug

When running Amplify pull headless and amplify pull on a existing studio app in powerhell the following error is thrown

🛑 FeatureFlags is not initialized

When using a headless pull, noticed the application does not prompt for a allow modify backend, throws error. Then pull fails entirely.

On existing application create by amplify CLI and then studio enabled the pull will throw the error after the UI components have been synched.

Edit your schema at C:\amplify\studioApps\taskapp\amplify\backend\api\taskapp\schema.graphql or place .graphql files in a directory at C:\amplify\studioApps\taskapp\amplify\backend\api\taskapp\schema
√ Successfully pulled backend environment dev from the cloud.
Browserslist: caniuse-lite is outdated. Please run:
  npx browserslist@latest --update-db
  Why you should do it regularly: https://github.com/browserslist/browserslist#browsers-data-updating
✅ 
√ Synced UI components.
⚠️ The components ItemCardCollection were synced with an older version of Amplify Studio. Please re-sync your components with Figma to get latest features and changes.
✅ GraphQL schema compiled successfully.

Edit your schema at C:\amplify\studioApps\taskapp\amplify\backend\api\taskapp\schema.graphql or place .graphql files in a directory at C:\amplify\studioApps\taskapp\amplify\backend\api\taskapp\schema
🛑 FeatureFlags is not initialized

** Note: when testing this in WSL the application works as expected.

Expected behavior

pull works in powershell

Reproduction steps

Amplify headless

1. create studio app
2. open powershell
3. amplify pull

Amplify pull

1. open powershell
2. amplify init
3. enable studio
4. create a data model
5. create forms in UI builder
6. amplify pull

GraphQL schema(s)

# Put schemas below this line

Project Identifier

6c986368d58e7b7a74f2a89d48b57947

Log output

# Put your logs below this line

Additional information

No response

[jparksecurity]

I still see this bug on version 11.0.2 when pushing the backend. I've seen this bug occasionally last a few months.

My workaround was to upgrade cli version.