Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Duplicated files generated from amplify env pull --restore

See original GitHub issue

Issue/question I am setting up an amplify project. I cloned a existing git repo first. And I ran amplify configure within my project folder and created a new IAM user on aws. After that, I ran amplify init and select a existing environment that have been created by my colleagues to initialize my amplify project.

The problem is when I ran amplify env pull --restore, there will be duplicated files generated in several minutes. For a file named "file.json’, the file with duplicated content will be “files 2.json”. Always have a number like 2 or 3 appending at the end of the previous filename.

Additional information OS: macOS Mojave node version: 12.16.1 aws-amplify: ^1.1.36

I found a similar issues here but is not exactly same to my situation: https://github.com/aws-amplify/amplify-cli/issues/3153

Issue Analytics

State:
Created 4 years ago
Reactions:2
Comments:19 (9 by maintainers)

Top GitHub Comments

1reaction

112Crackercommented, Oct 31, 2020

The reason for this issue is not because of Amplify CLI I think. It is because I iCloud sync was enabled on my laptop. details see incloud sync creating duplicate files when saving. After I disabled it, this issue is gone @brandonking7 @jhockett

0reactions

github-actions[bot]commented, May 25, 2021

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.

Top Results From Across the Web

AWS Amplify Duplicate Error: Duplicated files or mocks

Based on what I have read, #current-cloud-backend gets created by amplify, based on the files in the backend folder.

Quickstart

Insert amplify folder structure into the project's root directory, with the initial project configuration; Generate the project metadata files, with the outputs ...

Complete Guide to AWS Amplify Studio - Enlear Academy

Here's a glimpse of what we are going to do in this tutorial. Table of Content. Introduction; Setting Up the Project; UI Development;...

Troubleshooting AWS CodeBuild

Apache Maven builds reference artifacts from the wrong repository. Issue: When you use Maven with an AWS CodeBuild-provided Java build environment, Maven pulls...

Pull subscriptions | Cloud Pub/Sub Documentation

You might use the low-level auto-generated client library and synchronous pull in cases where using the Pull API directly makes sense. For ...