error when i do awsmobile pull #123

stevemao · 2018-05-04T08:41:02Z

awsmobile project's access information copied to: src/aws-exports.js
contents in #current-backend-info/ is synchronized with the latest in the aws cloud
? sync corresponding contents in backend/ with #current-backend-info/ Yes
(node:82217) UnhandledPromiseRejectionWarning: Error: EEXIST: file already exists, symlink '../mime/cli.js' -> '/Users/stevemao/workdir/news/awsmobilejs/backend/cloud-api/Posts/node_modules/.bin/mime'

Any idea why?

The text was updated successfully, but these errors were encountered:

UnleashedMind · 2018-05-04T17:35:17Z

We are investigating this issue.
This happens at the last step of the pull, the cli is updating the backend (your development) contents with the latest. So the contents in the #current-backend-info is already sync'ed up with the cloud.

UnleashedMind · 2018-05-04T18:23:22Z

What is your cli and node version?
I was not able to reproduce this error, with the same symlink in the node_modules/.bin folder.

stevemao · 2018-05-04T22:08:00Z

$ node -v
v10.0.0

$ npm -v
6.0.0

I tried

$ node -v
v6.10.3

$ npm -v
6.0.0

It gave me the same result.

My system: macOS High Sierra 10.13.2

My dependencies in one of the cloud apis:

"dependencies": {
    "amazon-cognito-identity-js": "^1.16.0",
    "aws-sdk": "^2.49.0",
    "aws-serverless-express": "^3.2.0",
    "body-parser": "^1.17.1",
    "elasticsearch": "^14.2.2",
    "express": "^4.15.2",
    "http-aws-es": "^4.0.0"
  },
  "devDependencies": {},

UnleashedMind · 2018-05-07T18:53:06Z

the cli only works for node version 7+, so node version 6.* is not a good choice.
Could you please try to use node version 8.9.0? That's the version that's been extensively tested. We haven't tested on node version 10.0.0 yet.

stevemao · 2018-05-07T22:12:34Z

I will switch to v8.9.0 and let you know.

…

Sent from my iPhone

On 8 May 2018, at 4:53 am, UnleashedMind ***@***.***> wrote: the cli only works for node version 7+, so node version 6.* is not a good choice. Could you please try to use node version 8.9.0? That's the version that's been extensively tested. We haven't tested on node version 10.0.0 yet. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

stevemao · 2018-05-08T01:41:51Z

I just tried it gives me the same result

$ npm version
{ 
  npm: '6.0.0',
  ares: '1.10.1-DEV',
  cldr: '32.0',
  http_parser: '2.7.0',
  icu: '60.1',
  modules: '57',
  nghttp2: '1.25.0',
  node: '8.10.0',
  openssl: '1.0.2n',
  tz: '2017c',
  unicode: '10.0',
  uv: '1.19.1',
  v8: '6.2.414.50',
  zlib: '1.2.11' }

retrieving the latest backend awsmobile project information
awsmobile project's details logged at:
    awsmobilejs/#current-backend-info/backend-details.json
awsmobile project's specifications logged at:
    awsmobilejs/#current-backend-info/mobile-hub-project.yml
awsmobile project's access information logged at:
    awsmobilejs/#current-backend-info/aws-exports.js
awsmobile project's access information copied to:
    src/aws-exports.js
contents in #current-backend-info/ is synchronized with the latest in the aws cloud
fs.js:1014
  return binding.symlink(preprocessSymlinkDestination(target, type, path),
                 ^

Error: EEXIST: file already exists, symlink '../mime/cli.js' -> '/Users/stevemao/workdir/news/awsmobilejs/backend/cloud-api/QueryPosts/node_modules/.bin/mime'
    at Object.fs.symlinkSync (fs.js:1014:18)
    at copySync (/Users/stevemao/.nvm/versions/node/v8.10.0/lib/node_modules/awsmobile-cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:58:8)
    at contents.forEach.content (/Users/stevemao/.nvm/versions/node/v8.10.0/lib/node_modules/awsmobile-cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:54:7)
    at Array.forEach (<anonymous>)
    at copySync (/Users/stevemao/.nvm/versions/node/v8.10.0/lib/node_modules/awsmobile-cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:51:14)
    at contents.forEach.content (/Users/stevemao/.nvm/versions/node/v8.10.0/lib/node_modules/awsmobile-cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:54:7)
    at Array.forEach (<anonymous>)
    at copySync (/Users/stevemao/.nvm/versions/node/v8.10.0/lib/node_modules/awsmobile-cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:51:14)
    at contents.forEach.content (/Users/stevemao/.nvm/versions/node/v8.10.0/lib/node_modules/awsmobile-cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:54:7)
    at Array.forEach (<anonymous>)

codeyogi911 · 2018-05-22T12:49:31Z

Hi i am also facing the same issue:

contents in #current-backend-info/ is synchronized with the latest in the aws cloud
fs.js:1014
  return binding.symlink(preprocessSymlinkDestination(target, type, path),
                 ^

Error: EEXIST: file already exists, symlink '../uuid/bin/uuid' -> '/Users/shashwatjain/Projects/Ionic/myApp/awsmobilejs/backend/cloud-api/imageplumber/node_modules/.bin/uuid'
    at Object.fs.symlinkSync (fs.js:1014:18)
    at copySync (/usr/local/lib/node_modules/awsmobile-cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:58:8)
    at contents.forEach.content (/usr/local/lib/node_modules/awsmobile-cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:54:7)
    at Array.forEach (<anonymous>)
    at copySync (/usr/local/lib/node_modules/awsmobile-cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:51:14)
    at contents.forEach.content (/usr/local/lib/node_modules/awsmobile-cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:54:7)
    at Array.forEach (<anonymous>)
    at copySync (/usr/local/lib/node_modules/awsmobile-cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:51:14)
    at contents.forEach.content (/usr/local/lib/node_modules/awsmobile-cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:54:7)
    at Array.forEach (<anonymous>)

stevekinney · 2018-05-29T18:24:54Z

Do y'all have anything custom going on in your Cloud APIs?

stevemao · 2018-05-29T23:08:50Z

@stevekinney no

dylan-westbury · 2018-06-05T10:30:31Z

Me too, node LTS and new aws amplify project.

New to awsmobile... what could be wrong?


    src/aws-exports.js
contents in #current-backend-info/ is synchronized with the latest in the aws cloud
fs.js:1014
  return binding.symlink(preprocessSymlinkDestination(target, type, path),
                 ^

Error: EEXIST: file already exists, symlink '../mime/cli.js' -> '/xxxx/wesbite/awsmobilejs/backend/cloud-api/sampleLambda/node_modules/.bin/mime'
    at Object.fs.symlinkSync (fs.js:1014:18)
    at copySync (/Users/Dylan/.nvm/versions/node/v8.11.2/lib/node_modules/awsmobile-cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:58:8)
    at contents.forEach.content (/Users/Dylan/.nvm/versions/node/v8.11.2/lib/node_modules/awsmobile-cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:54:7)
    at Array.forEach (<anonymous>)
    at copySync (/Users/Dylan/.nvm/versions/node/v8.11.2/lib/node_modules/awsmobile-cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:51:14)
    at contents.forEach.content (/Users/Dylan/.nvm/versions/node/v8.11.2/lib/node_modules/awsmobile-cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:54:7)
    at Array.forEach (<anonymous>)
    at copySync (/Users/Dylan/.nvm/versions/node/v8.11.2/lib/node_modules/awsmobile-cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:51:14)
    at contents.forEach.content (/Users/Dylan/.nvm/versions/node/v8.11.2/lib/node_modules/awsmobile-cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:54:7)
    at Array.forEach (<anonymous>)

website Dylan$ node -v
v8.11.2

ianpogi5 · 2018-06-14T00:30:14Z

Here's mine:

contents in #current-backend-info/ is synchronized with the latest in the aws cloud
fs.js:1014
  return binding.symlink(preprocessSymlinkDestination(target, type, path),
                 ^

Error: EEXIST: file already exists, symlink '../../../../../../../semver/bin/semver' -> '/xxxx/awsmobilejs/backend/cloud-api/jobs/node_modules/.bin/semver'
    at Object.fs.symlinkSync (fs.js:1014:18)
    at copySync (/usr/local/lib/node_modules/awsmobile-cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:58:8)
    at contents.forEach.content (/usr/local/lib/node_modules/awsmobile-cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:54:7)
    at Array.forEach (<anonymous>)
    at copySync (/usr/local/lib/node_modules/awsmobile-cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:51:14)
    at contents.forEach.content (/usr/local/lib/node_modules/awsmobile-cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:54:7)
    at Array.forEach (<anonymous>)
    at copySync (/usr/local/lib/node_modules/awsmobile-cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:51:14)
    at contents.forEach.content (/usr/local/lib/node_modules/awsmobile-cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:54:7)
    at Array.forEach (<anonymous>)

node v8.11.2
npm v5.6.0

ianpogi5 · 2018-06-14T05:43:13Z

Here's what I did to recreate the problem.

Create the App in the Mobile Hub AWS console.
Enable Cloud logic.
Create new API.
On your project source code, awsmobile init projectid
awsmobile pull
cd awsmobile/backend/cloud-api/your-api-folder/
Create package.json file
npm install aws-sdk --save
Go back to root folder of your project
awmobile push

jtnix · 2018-06-29T20:54:18Z

Same for me, nothing super custom going on, but I did manually change the remote AWS node version to 8.10 for all API routes in the mobile-hub-project.yml file just before it started happening:

contents in #current-backend-info/ is synchronized with the latest in the aws cloud
fs.js:143
    throw err;
    ^

Error: EEXIST: file already exists, symlink '../uuid/bin/uuid' -> '/Users/xxx/react/xxx/awsmobilejs/backend/cloud-api/xxx/node_modules/.bin/uuid'
    at Object.fs.symlinkSync (fs.js:1000:3)
    at copySync (/usr/local/lib/node_modules/awsmobile-cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:58:8)
    at contents.forEach.content (/usr/local/lib/node_modules/awsmobile-cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:54:7)
    at Array.forEach (<anonymous>)
    at copySync (/usr/local/lib/node_modules/awsmobile-cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:51:14)
    at contents.forEach.content (/usr/local/lib/node_modules/awsmobile-cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:54:7)
    at Array.forEach (<anonymous>)
    at copySync (/usr/local/lib/node_modules/awsmobile-cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:51:14)
    at contents.forEach.content (/usr/local/lib/node_modules/awsmobile-cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:54:7)
    at Array.forEach (<anonymous>)

When I remove the node_modules from the awsmobilejs/backend/cloud-api/xxx folder, and re-run awsmobile push I get a similar error, but from within a different 'package' this time:

Error: EEXIST: file already exists, symlink '../mime/cli.js' -> '/Users/xxx/react/xxx/awsmobilejs/backend/cloud-api/xxx/node_modules/.bin/mime'
    at Object.fs.symlinkSync (fs.js:1000:3)
    at copySync (/usr/local/lib/node_modules/awsmobile-cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:58:8)
    at contents.forEach.content (/usr/local/lib/node_modules/awsmobile-cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:54:7)
    at Array.forEach (<anonymous>)
    at copySync (/usr/local/lib/node_modules/awsmobile-cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:51:14)
    at contents.forEach.content (/usr/local/lib/node_modules/awsmobile-cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:54:7)
    at Array.forEach (<anonymous>)
    at copySync (/usr/local/lib/node_modules/awsmobile-cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:51:14)
    at contents.forEach.content (/usr/local/lib/node_modules/awsmobile-cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:54:7)
    at Array.forEach (<anonymous>)

The deployed serverless code still works for me in any case, it's just a confusing error!

realadeel · 2018-07-04T06:02:18Z

Getting something similar when running "awsmobile push". Last thing I did was npm install a new library ("getstream"). Uninstalling it and re-pushing did not fix the error.

node v9.2.0
npm v5.5.1

=====
contents in #current-backend-info/ is synchronized with the latest in the aws cloud
fs.js:1034
return binding.symlink(preprocessSymlinkDestination(target, type, path),
^

Error: EEXIST: file already exists, symlink '../sshpk/bin/sshpk-conv' -> '/Users/xxx/projects/xxx/awsmobilejs/backend/cloud-api/API/node_modules/.bin/sshpk-conv'
at Object.fs.symlinkSync (fs.js:1034:18)
at copySync (/usr/local/lib/node_modules/awsmobile-cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:58:8)
at contents.forEach.content (/usr/local/lib/node_modules/awsmobile-cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:54:7)
at Array.forEach ()
at copySync (/usr/local/lib/node_modules/awsmobile-cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:51:14)
at contents.forEach.content (/usr/local/lib/node_modules/awsmobile-cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:54:7)
at Array.forEach ()
at copySync (/usr/local/lib/node_modules/awsmobile-cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:51:14)
at contents.forEach.content (/usr/local/lib/node_modules/awsmobile-cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:54:7)
at Array.forEach ()

realadeel · 2018-07-04T06:12:22Z

This worked for me:
remove node_modules
npm install --no-bin-links

Inspiration: TritonDataCenter/node-sshpk#16

stevemao · 2018-07-05T00:16:02Z

This worked for me:
remove node_modules
npm install --no-bin-links

Yup, I googled it and saw that too... Seems like a workaround, not a fix.

jbarwick · 2018-07-05T04:40:16Z

My experience was that it fixed the immediate push. But, if you have pushed these symlinks before, the lambda function will fail with deception causing a cloud formation infinite loop and inability to update or fix the problem without deleting the entire stack and rebuild after manually deleting the #current-backend-Info and .awsmobile/build-info directories. But even that might not work and you might need to delete the entire cloud formation stack and restart from scratch. But then the mobile-hub-project.yml might be out of sync and and might be impossible to re-sync. Good luck!

…

Sent from my iPhone

On 5 Jul 2018, at 8:16 AM, Steve Mao ***@***.***> wrote: This worked for me: remove node_modules npm install --no-bin-links Yup, I googled it and saw that too... Seems like a work around not a fix. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

stevemao · 2018-09-05T14:04:59Z

I want to emphasize that this issue is really critical... awsmobile publish is completely broken.

barrypeterson · 2018-09-19T08:48:31Z

Same issue: -- Lmk how I can help!

awsmobile project's access information copied to:
    app/aws-exports.js
contents in #current-backend-info/ is synchronized with the latest in the aws cloud
fs.js:1014
  return binding.symlink(preprocessSymlinkDestination(target, type, path),
                 ^

Error: EEXIST: file already exists, symlink '../mime/cli.js' -> '/Users/bpeterson/Projects/notify/awsmobilejs/backend/cloud-api/messages/node_modules/.bin/mime'
    at Object.fs.symlinkSync (fs.js:1014:18)
    at copySync (/Users/bpeterson/.nvm/versions/node/v8.11.3/lib/node_modules/awsmobile-cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:58:8)
    at contents.forEach.content (/Users/bpeterson/.nvm/versions/node/v8.11.3/lib/node_modules/awsmobile-cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:54:7)
    at Array.forEach (<anonymous>)
    at copySync (/Users/bpeterson/.nvm/versions/node/v8.11.3/lib/node_modules/awsmobile-cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:51:14)
    at contents.forEach.content (/Users/bpeterson/.nvm/versions/node/v8.11.3/lib/node_modules/awsmobile-cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:54:7)
    at Array.forEach (<anonymous>)
    at copySync (/Users/bpeterson/.nvm/versions/node/v8.11.3/lib/node_modules/awsmobile-cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:51:14)
    at contents.forEach.content (/Users/bpeterson/.nvm/versions/node/v8.11.3/lib/node_modules/awsmobile-cli/node_modules/fs-extra/lib/copy-sync/copy-sync.js:54:7)
    at Array.forEach (<anonymous>)

nishanthk · 2018-10-18T06:49:08Z

Is there a fix for this, having same issue

idevelop · 2019-01-24T17:55:27Z

Still an issue in 2019 :)

nawwa · 2019-02-12T13:43:20Z

Yes still an issue .. awsmobile push give
Error: EEXIST: file already exists, symlink '../json2csv/bin/json2csv.js' ->

:(

automatication · 2019-02-12T21:26:24Z

Removed node_modules and did:
npm install --no-bin-links

Seems to work for me.

nawwa · 2019-04-25T07:54:17Z

@automatication same, worked today :)

shivaramani · 2019-05-09T18:20:08Z

Still getting the error. Any other workarounds?
Not working with removing nodemodules and npm install --no-bin-links

Error: EEXIST: file already exists, symlink '../uuid/bin/uuid' -> '//node_modules/aws-sdk/node_modules/.bin/uuid'

at /node_modules/fs-extra/lib/copy-sync/copy-sync.js:54:7

UnleashedMind added the investigating label May 4, 2018

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

error when i do awsmobile pull #123

error when i do awsmobile pull #123

stevemao commented May 4, 2018

UnleashedMind commented May 4, 2018

UnleashedMind commented May 4, 2018

stevemao commented May 4, 2018 •

edited

Loading

UnleashedMind commented May 7, 2018

stevemao commented May 7, 2018 via email

stevemao commented May 8, 2018

codeyogi911 commented May 22, 2018

stevekinney commented May 29, 2018

stevemao commented May 29, 2018

dylan-westbury commented Jun 5, 2018 •

edited

Loading

ianpogi5 commented Jun 14, 2018

ianpogi5 commented Jun 14, 2018

jtnix commented Jun 29, 2018

realadeel commented Jul 4, 2018

realadeel commented Jul 4, 2018

stevemao commented Jul 5, 2018 •

edited

Loading

jbarwick commented Jul 5, 2018 via email

stevemao commented Sep 5, 2018

barrypeterson commented Sep 19, 2018

nishanthk commented Oct 18, 2018

idevelop commented Jan 24, 2019

nawwa commented Feb 12, 2019

automatication commented Feb 12, 2019 •

edited

Loading

nawwa commented Apr 25, 2019

shivaramani commented May 9, 2019

error when i do awsmobile pull #123

error when i do awsmobile pull #123

Comments

stevemao commented May 4, 2018

UnleashedMind commented May 4, 2018

UnleashedMind commented May 4, 2018

stevemao commented May 4, 2018 • edited Loading

UnleashedMind commented May 7, 2018

stevemao commented May 7, 2018 via email

stevemao commented May 8, 2018

codeyogi911 commented May 22, 2018

stevekinney commented May 29, 2018

stevemao commented May 29, 2018

dylan-westbury commented Jun 5, 2018 • edited Loading

ianpogi5 commented Jun 14, 2018

ianpogi5 commented Jun 14, 2018

jtnix commented Jun 29, 2018

realadeel commented Jul 4, 2018

realadeel commented Jul 4, 2018

stevemao commented Jul 5, 2018 • edited Loading

jbarwick commented Jul 5, 2018 via email

stevemao commented Sep 5, 2018

barrypeterson commented Sep 19, 2018

nishanthk commented Oct 18, 2018

idevelop commented Jan 24, 2019

nawwa commented Feb 12, 2019

automatication commented Feb 12, 2019 • edited Loading

nawwa commented Apr 25, 2019

shivaramani commented May 9, 2019

stevemao commented May 4, 2018 •

edited

Loading

dylan-westbury commented Jun 5, 2018 •

edited

Loading

stevemao commented Jul 5, 2018 •

edited

Loading

automatication commented Feb 12, 2019 •

edited

Loading