Closed lebull closed 3 years ago
@lebull thanks for reporting the issue we're aware of this and it will be fixed in the next release.
4.39 seemed to resolve this issue.
@lebull Thanks for checking
Im getting this issue on 4.39
`amplify pull
Pre-pull status:
Current Environment: staging
Category | Resource name | Operation | Provider plugin |
---|---|---|---|
Api | OperationCookies | No Change | awscloudformation |
/ Fetching updates to backend environment: staging from the cloud.Could not initialize 'staging': EPERM: operation not permitted, stat 'C:\Users\Berbaroovez\Desktop\ReactProjects\cookiemanager\amplify\backend'`
This issue has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs.
Looking for a help forum? We recommend joining the Amplify Community Discord server *-help
channels for those types of questions.
This is happening on Windows.
Describe the bug A clear and concise description of what the bug is.
Pulling env created by the amplify console results in a permissions error
Amplify CLI Version You can use
amplify -v
to check the amplify cli version on your systemTo Reproduce Steps to reproduce the behavior or terminal output if applicable
Additional context Add any other context about the problem here.
I originally had this pointed to another amplify project in another branch, so maybe something wanky happened with the cli's config? But I'm reproducing this after creating a fresh clone on a different machine where there was never a reference to the other project.