Deploying on AWS Amplify, NPM Error "authentication token not provided" #398

kirkHawksworth · 2025-01-24T14:24:28Z

kirkHawksworth
Jan 24, 2025

I am attempting to build my app from AWS Amplify.

The build is created with an amplify.yml which, by default looks like this;

I have added my token which I got from Polar to the environment variables section within Amplify;

I then edited the amplify.yml to use this token;

However, I still receive this error;

npm ERR! 401 Unauthorized - GET https://npm.pkg.github.com/download/@capawesome-team/capacitor-nfc/6.1.0/bc14e06333969038e1193ccc7429b2f66de342bc - authentication token not provided

Can anyone help?

p.s. I pasted images, as I couldn't get the code formatting to work when I pasted yaml.

Here is my amplify.yml code;

version: 1
frontend:
  phases:
    preBuild:
      commands:
        - npm ci --cache .npm --prefer-offline
        - echo "@capawesome-team:registry=https://npm.registry.capawesome.io" >> .npmrc
        - echo "//npm.registry.capawesome.io/:_authToken=${CAPAWESOME_TOKEN}" >> .npmrc
    build:
      commands:
        - npm run build
  artifacts:
    baseDirectory: dist
    files:
      - '**/*'
  cache:
    paths:
      - .npm/**/*`

Answered by kirkHawksworth

Jan 24, 2025

Yes sure, I will add it as an answer here.

The amplify.yml file:

version: 1
frontend:
  phases:
    preBuild:
      commands:
        - echo "" >> .npmrc
        - echo "@capawesome-team:registry=https://npm.registry.capawesome.io" >> .npmrc
        - echo "//npm.registry.capawesome.io/:_authToken=${CAPAWESOME_TOKEN}" >> .npmrc
        - npm ci
    build:
      commands:
        - npm run build
  artifacts:
    baseDirectory: dist
    files:
      - '**/*'
  cache:
    paths:
      - .npm/**/*

I am not certain that ' echo "" >> .npmrc' is required, but it does no harm and I had a hunch it intermittently wasn't being cleared properly between builds.

I add the ${CAPAWESOME_TOKEN} to the env…

View full answer

robingenz · 2025-01-24T14:32:16Z

robingenz
Jan 24, 2025
Maintainer

You should set the token before running npm ci:

version: 1
frontend:
  phases:
    preBuild:
      commands:
-       - npm ci --cache .npm --prefer-offline
        - echo "@capawesome-team:registry=https://npm.registry.capawesome.io" >> .npmrc
        - echo "//npm.registry.capawesome.io/:_authToken=${CAPAWESOME_TOKEN}" >> .npmrc
+       - npm ci --cache .npm --prefer-offline
    build:
      commands:
        - npm run build
  artifacts:
    baseDirectory: dist
    files:
      - '**/*'
  cache:
    paths:
      - .npm/**/*`

Let me know if that helps.

0 replies

kirkHawksworth · 2025-01-24T15:03:16Z

kirkHawksworth
Jan 24, 2025
Author

Thank you for the quick response! I have put those in the correct order now, but I still receive the same error.

I have edited my amplify.yml to logout what is in .npmrc and it now looks like;

version: 1
frontend:
  phases:
    preBuild:
      commands:
        - echo "CAPAWESOME_TOKEN=${CAPAWESOME_TOKEN}"
        - echo "" > .npmrc
        - cat .npmrc
        - echo "@capawesome-team:registry=https://npm.registry.capawesome.io" >> .npmrc
        - echo "//npm.registry.capawesome.io/:_authToken=${CAPAWESOME_TOKEN}" >> .npmrc
        - cat .npmrc
        - npm ci --cache .npm --prefer-offline
    build:
      commands:
        - npm run build
  artifacts:
    baseDirectory: dist
    files:
      - '**/*'
  cache:
    paths:
      - .npm/**/*

 # Starting phase: preBuild
 # Executing command: echo "CAPAWESOME_TOKEN=${CAPAWESOME_TOKEN}"
CAPAWESOME_TOKEN=POLAR-my-token
# Executing command: echo "" > .npmrc
2025-01-24T14:54:17.281Z [INFO]: # Executing command: cat .npmrc
2025-01-24T14:54:17.283Z [INFO]:
2025-01-24T14:54:17.283Z [INFO]: # Executing command: echo "@capawesome-team:registry=https://npm.registry.capawesome.io" >> .npmrc
# Executing command: echo "//npm.registry.capawesome.io/:_authToken=${CAPAWESOME_TOKEN}" >> .npmrc
# Executing command: cat .npmrc
2025-01-24T14:54:17.286Z [INFO]: @capawesome-team:registry=https://npm.registry.capawesome.io
//npm.registry.capawesome.io/:_authToken=POLAR-my-token
# Executing command: npm ci --cache .npm --prefer-offline
2025-01-24T14:54:31.492Z [WARNING]: npm WARN registry No auth for URI, but auth present for scoped registry.
npm
2025-01-24T14:54:31.501Z [WARNING]: WARN registry
npm WARN registry URI: https://npm.pkg.github.com/download/@capawesome-team/capacitor-nfc/6.1.0/bc14e06333969038e1193ccc7429b2f66de342bc
npm WARN registry Scoped Registry Key: //npm.registry.capawesome.io/
npm WARN registry
npm WARN registry More info here: https://github.com/npm/cli/wiki/No-auth-for-URI,-but-auth-present-for-scoped-registry
2025-01-24T14:54:42.943Z [WARNING]: npm ERR! code E401
2025-01-24T14:54:42.949Z [WARNING]: npm ERR! 401 Unauthorized - GET https://npm.pkg.github.com/download/@capawesome-team/capacitor-nfc/6.1.0/bc14e06333969038e1193ccc7429b2f66de342bc - authentication token not provided
npm ERR! A complete log of this run can be found in: /codebuild/output/src1291407842/src/CheckedSafeMobileCapacitor/.npm/_logs/2025-01-24T14_54_25_689Z-debug-0.log
2025-01-24T14:54:43.013Z [ERROR]: !!! Build failed
2025-01-24T14:54:43.013Z [ERROR]: !!! Error: Command failed with exit code 1
2025-01-24T14:54:43.013Z [INFO]: # Starting environment caching...
2025-01-24T14:54:43.013Z [INFO]: # Environment caching completed

Thank you for your help with this issue, I realise this isn't a capawesome issue so I do appreciate it

3 replies

robingenz Jan 24, 2025
Maintainer

Have you tried using the "npm config" command like in this post?

npm config set @capawesome-team:registry https://npm.registry.capawesome.io
npm config set //npm.registry.capawesome.io/:_authToken <YOUR_LICENSE_KEY>

kirkHawksworth Jan 24, 2025
Author

Sorry Robin that didn't work either, same error:

# Executing command: npm config set @capawesome-team:registry https://npm.registry.capawesome.io
2025-01-24T15:19:21.189Z [INFO]: # Executing command: npm config set //npm.registry.capawesome.io/:_authToken=POLAR-the-code
2025-01-24T15:19:21.467Z [INFO]: # Executing command: npm ci --cache .npm --prefer-offline
2025-01-24T15:19:38.412Z [WARNING]: npm
2025-01-24T15:19:38.420Z [WARNING]: ERR! code E401
npm ERR! 401 Unauthorized - GET https://npm.pkg.github.com/download/@capawesome-team/capacitor-nfc/6.1.0/bc14e06333969038e1193ccc7429b2f66de342bc - authentication token not providednpm ERR! A complete log of this run

robingenz Jan 24, 2025
Maintainer

Please also run "npm config set always-auth true" and omit the "--cache .npm --prefer-offline". Maybe that helps.

kirkHawksworth · 2025-01-24T17:30:13Z

kirkHawksworth
Jan 24, 2025
Author

I think I have found the route cause of the issue...

I created a brand new project from scratch, used your commands and it worked. I checked the package-lock.json

    "node_modules/@capawesome-team/capacitor-nfc": {
      "version": "6.5.1",
      "resolved": "https://npm.registry.capawesome.io/download/@capawesome-team/capacitor-nfc/6.5.1/1e5f631dabb8d7c6163731064bb3416f095c3382",
      "integrity": "sha512-WeiqH2rROade61v0Y/6pBVNSCkyrk3ElVL5vGYk7gCKHjcBvP2w0z4po8eKKAcJGr3HTp19JaInPxycrXO/bVg==",
      "peerDependencies": {
        "@capacitor/core": "^6.0.0"
      }
    }

But in the package-lock.json of my production app is

    "node_modules/@capawesome-team/capacitor-nfc": {
      "version": "6.1.0",
      "resolved": "https://npm.pkg.github.com/download/@capawesome-team/capacitor-nfc/6.1.0/bc14e06333969038e1193ccc7429b2f66de342bc",
      "integrity": "sha512-t9ddI+BYOBLahNlYZVSGh6YrcJIYBbz3qcguMO6geNjbldb75gEkex85LBDSliT8Kpdbvbuuwh5MLoZ08WcQVQ==",
      "peerDependencies": {
        "@capacitor/core": "^6.0.0"
      }
    }

Notice how the production version resolves to "npm.pkg.github.com" and the new app I created resolves to "npm.registry.capawesome.io".

Out of interest, do you know why this would be?

I uninstalled the "nfc" plugin, and then re-installed, which changed the package-lock to npm.registry and now the build works!

Thank you for your help

1 reply

robingenz Jan 24, 2025
Maintainer

You're welcome! That would have been my next guess. ^^ This issue occurs if you run the install command the first time without the proper registry configuration.

I would love to add an example configuration to the Capawesome site. Would you mind sharing your working configuration?

kirkHawksworth · 2025-01-24T17:46:43Z

kirkHawksworth
Jan 24, 2025
Author

Yes sure, I will add it as an answer here.

The amplify.yml file:

version: 1
frontend:
  phases:
    preBuild:
      commands:
        - echo "" >> .npmrc
        - echo "@capawesome-team:registry=https://npm.registry.capawesome.io" >> .npmrc
        - echo "//npm.registry.capawesome.io/:_authToken=${CAPAWESOME_TOKEN}" >> .npmrc
        - npm ci
    build:
      commands:
        - npm run build
  artifacts:
    baseDirectory: dist
    files:
      - '**/*'
  cache:
    paths:
      - .npm/**/*

I am not certain that ' echo "" >> .npmrc' is required, but it does no harm and I had a hunch it intermittently wasn't being cleared properly between builds.

I add the ${CAPAWESOME_TOKEN} to the environments variable page.

Here are the images, incase you want to use them in your documentation;

https://share.cleanshot.com/PpcM4JxZ

https://share.cleanshot.com/wtnzw0hp

1 reply

robingenz Jan 24, 2025
Maintainer

Awesome, thank you! 🙏🏻

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Deploying on AWS Amplify, NPM Error "authentication token not provided" #398

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 4 comments 5 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

Deploying on AWS Amplify, NPM Error "authentication token not provided" #398

kirkHawksworth Jan 24, 2025

Replies: 4 comments · 5 replies

robingenz Jan 24, 2025 Maintainer

kirkHawksworth Jan 24, 2025 Author

robingenz Jan 24, 2025 Maintainer

kirkHawksworth Jan 24, 2025 Author

robingenz Jan 24, 2025 Maintainer

kirkHawksworth Jan 24, 2025 Author

robingenz Jan 24, 2025 Maintainer

kirkHawksworth Jan 24, 2025 Author

robingenz Jan 24, 2025 Maintainer

kirkHawksworth
Jan 24, 2025

Replies: 4 comments 5 replies

robingenz
Jan 24, 2025
Maintainer

kirkHawksworth
Jan 24, 2025
Author

robingenz Jan 24, 2025
Maintainer

kirkHawksworth Jan 24, 2025
Author

robingenz Jan 24, 2025
Maintainer

kirkHawksworth
Jan 24, 2025
Author

robingenz Jan 24, 2025
Maintainer

kirkHawksworth
Jan 24, 2025
Author

robingenz Jan 24, 2025
Maintainer