amplify pull results in error: File at path '.../parameters.json' does not exist

[agrabz]

Describe the bug

I try to run amplify pull, but it results in error:
⠇ Fetching updates to backend environment: staging from the cloud.⠋ Building res✔ Successfully pulled backend environment staging from the cloud.
✖ There was an error initializing your environment.
🛑 File at path: '/Users//amplify/backend/auth//parameters.json' does not exist

And it's correct, because in my backend folder I have some kind of numbering going on. Running ls in backend folder:
amplify-meta 2.json awscloudformation storage 3
amplify-meta.json awscloudformation 2 tags 2.json
api awscloudformation 3 tags.json
api 3 backend-config 2.json types
auth 3 backend-config.json

As you see I have a lot of 2s and 3s, which I don't really get. I noticed that I have a similar numbering in the amplify folder as well:
#current-cloud-backend cli 3.json team-provider-info.json
backend cli.json
cli 2.json generated

And in my project folder as well:
Amplify amplify
amplify 2
README.md amplifyconfiguration.json
awsconfiguration.json
.xcodeproj graphql
UnitTests

I honestly don't know how I got here. Seemingly I horribly messed up everything. I tried to change my scheme and I might have done something that should have not been done. Is there a way for recovery?

Steps To Reproduce

Run `amplify pull`

Expected behavior

Remote changes are retrieved without any error. Or if there's an error then I should be able to have some recovery options.

Amplify Framework Version

How do find this?

Amplify Categories

API

Dependency manager

Swift PM

Swift version

5.9

CLI version

12.10.1

Xcode version

15.2

Relevant log output

I ran amplify diagnose --send-report 
Project Identifier: 8e4abdb4e99dc04c9ec936596118bd35

Is this a regression?

No

Regression additional context

No response

Platforms

iOS

OS Version

17.0

Device

iPhone 15 Pro

Specific to simulators

No response

Additional context

No response

[sebaland]

Hi @agrabz, thanks for opening this issue.
I've transferred it to the amplify-cli repo, as it seems to be an issue within Amplify CLI and not within Amplify Swift's scope.

[ykethan]

Hey @agrabz, from the information appears to be similar to #13335
is the project folder currently uses a cloud storage such as OneDrive, Google Drive or iCloud?
to mitigate the issue(#13335 (comment)) you can download the #current-cloud-backend.zip archive, unzip, carefully remove duplicate files, re-zip, and re-upload. note while re-zipping the files do ensure you are not creating a nested #current-cloud-backend folder but the contents of the folder at root.

[ykethan]

Closing the issue due to inactivity. Do reach out to us if you require any assistance.

[github-actions]

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.