[BUG]: NPMv1 ##[warning]Can't find loc string for key: Info_GotAndMaskAuth

[gavintoddchurch]

New issue checklist

• I searched for existing GitHub issues
• I read pipeline troubleshooting guide
• I checked how to collect logs

Task name

npm

Task version

1.241.1

Issue Description

In the latest version of the task there is warning ##[warning]Can't find loc string for key: Info_GotAndMaskAuth.

Environment type (Please select at least one enviroment where you face this issue)

• Self-Hosted
• Microsoft Hosted
• VMSS Pool
• Container

Azure DevOps Server type

dev.azure.com (formerly visualstudio.com)

Azure DevOps Server Version (if applicable)

No response

Operation system

Ubuntu 20.04

Relevant log output

==============================================================================
Task         : npm
Description  : Install and publish npm packages, or run an npm command. Supports npmjs.com and authenticated registries like Azure Artifacts.
Version      : 1.241.1
Author       : Microsoft Corporation
Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/package/npm
==============================================================================
##[debug]Resource Utilization warnings is disabled, switch "DISABLE_RESOURCE_UTILIZATION_WARNINGS" variable to "true" if you want to enable it
##[debug]Using node path: /agent/externals/node20_1/bin/node
##[debug]agent.TempDirectory=/agent/_work/_temp
##[debug]loading inputs and endpoints
##[debug]loading INPUT_COMMAND
##[debug]loading INPUT_WORKINGDIR
##[debug]loading INPUT_CUSTOMCOMMAND
##[debug]loading INPUT_CUSTOMREGISTRY
##[debug]loading INPUT_PUBLISHREGISTRY
##[debug]loading INPUT_PUBLISHPACKAGEMETADATA
##[debug]loading ENDPOINT_AUTH_SYSTEMVSSCONNECTION
##[debug]loading ENDPOINT_AUTH_SCHEME_SYSTEMVSSCONNECTION
##[debug]loading ENDPOINT_AUTH_PARAMETER_SYSTEMVSSCONNECTION_ACCESSTOKEN
##[debug]loading SECRET_SYSTEM_ACCESSTOKEN
##[debug]loaded 10
##[debug]Agent.ProxyUrl=undefined
##[debug]Agent.CAInfo=undefined
##[debug]Agent.ClientCert=undefined
##[debug]Agent.SkipCertValidation=undefined
##[debug]check path : /agent/_work/_tasks/Npm_fe47e961-9fa8-4106-8639-368c022d43ad/1.241.1/task.json
##[debug]adding resource file: /agent/_work/_tasks/Npm_fe47e961-9fa8-4106-8639-368c022d43ad/1.241.1/task.json
##[debug]system.culture=en-US
##[debug]Getting Packaging service access points
##[debug]System.TeamFoundationCollectionUri=https://dev.azure.com/<redacted>
##[debug]System.ServerType=Hosted
##[debug]Getting credentials for local feeds
##[debug]SYSTEMVSSCONNECTION exists true
##[warning]Can't find loc string for key: Info_GotAndMaskAuth
##[debug]Processed: ##vso[task.issue type=warning;]Can't find loc string for key: Info_GotAndMaskAuth
##[debug]Info_GotAndMaskAuth

### Full task logs with system.debug enabled

<details>
  <pre> [REPLACE THIS WITH YOUR INFORMATION] </pre>
</details>


### Repro steps

```yml
Run any npm@1 task for example
            - task: Npm@1
              displayName: Install dependencies
              inputs:
                command: ci

[anthonywhite]

also getting this on version 0.242.1

[somphouang]

also getting same issue on npmAuthenticate@0 task with same setup self host

[krisrm]

Same issue, npmAuthenticate@0 , 0.242.0

[ericbenhumayo]

I'm also seeing this issue with npm install version 1.241.1

[ejsamson05]

We also have this issue. Any updates?

[SchulteDev]

Related

1. [BUG]: NPM@1: "Can't find loc string for key: Info_GotAndMaskAuth" #20120
2. https://developercommunity.visualstudio.com/t/When-running-my-build-pipeline-im-gettin/10699373?sort=active&topics=NodeJS

[eduardofontes]

Task : Universal packages
Description : Download or publish Universal Packages
Version : 0.242.1

##[warning]Can't find loc string for key: Info_GotAndMaskAuth

##[error]Error: ENOENT: no such file or directory, chmod '/opt/hostedtoolcache/ArtifactTool/0.2.344/x64/Artifacttool'

The pipeline is broken since today. Don't know it is related to this issue.

[jonasbbernardi]

Same issue with Universal packages

[micaelvitor]

For a temporary fix just change the task version to 0.228.0

example:

- task: [email protected]

[probststefan]

Does anyone have a solution to get npmAuthenticate@0 to work again?

[SchulteDev]

Does anyone have a solution to get npmAuthenticate@0 to work again?

No :-(
Downgrading to [email protected] failed: "A task is missing. The pipeline references a task called 'npmAuthenticate'. This usually indicates the task isn't installed, and you may be able to install it from the Marketplace: https://marketplace.visualstudio.com. (Task version 0.228.0, job 'build', step ''.)"
In our pipeline, last working npmAuthenticate was 0.238.2. But even downgrading to 0.238.2 does not help., the following npm ci still fails with 401 when connecting to our private NPM registry.

[KristofKuli]

As a workaround, you can try using the previous version, 1.238.1.

• task: [email protected]
  inputs:
  command: 'install'

[MicroTuld]

Task : Universal packages Description : Download or publish Universal Packages Version : 0.242.1

##[warning]Can't find loc string for key: Info_GotAndMaskAuth

##[error]Error: ENOENT: no such file or directory, chmod '/opt/hostedtoolcache/ArtifactTool/0.2.344/x64/Artifacttool'

The pipeline is broken since today. Don't know it is related to this issue.

Though UniversalPackagesV0 is also having these warnings, that it is breaking was due to another reason, fixed here: microsoft/azure-pipelines-tasks-common-packages#354
#20148

The fix should be released with versions 0.243.0+.

[rLindorfer]

Same issue with 1.241.1

[aarontravass]

Same issue with 1.241.1

Same for me as well. Node version is 20.

[tsulli]

We're seeing the same NPM warning with task version 1.241.1, agent version 3.241.0

[ganeshg2491]

We are seeing same warning with NPM@1 task (1.242.1)

This pull request indicates that the issues have been addressed, but it appears that the problem still persists.
microsoft/azure-pipelines-tasks-common-packages#345

[gavintoddchurch]

I believe they would need to deploy a new version for that to get change to get added into the task.

[mapau]

We are seeing same warning with npmAuthenticate 0.242.0 and Agent name: 'Hosted Agent' Current agent version: '3.241.0'

using [email protected] fix the warning output

[shiraze]

Same issue with Universal packages

I've raised #20203 to track Universal Packages

[gavintoddchurch]

is there a plan to release a new version of the task with the fix that seems to be merged into the repo?

[pdzienisiewicz]

Will there be a fix implemented on official npm?
I still get an error when installing the latest npm [warning]Can't find loc string for key: Info_GotAndMaskAuth using npm install via Azure Pipelines (currently showing 1.242.1).

[bpaithari]

We also have this issue. Any updates?

[tintse-thxsky-MSFT]

hi all, the problem should be resolved now. Please reopen this if it happens again.

[aarontravass]

hi all, the problem should be resolved now. Please reopen this if it happens again.

Do we need to migrate to a new version?

Edit: an update was not required from our end. Works fine now.

[bdbvb]

still happening here

[lavi09]

still happening for npm authenticate 0.242.0

[gavintoddchurch]

I think they'll have to do a new release to get the new version.

[MirKml]

It seems that @tintse-thxsky-MSFT fixed this by this one #20259.
There is so much npm packages which are used here and there. Somebody fixes one, but it's necessary to bump others .... seems only msft tech stuff knows the right dependencies.

Maybe "azure-pipelines-task" package is the right one, which will be later used in pipeline agent (🙏).

[tintse-thxsky-MSFT]

still happening here

may you post your pipeline log?

[bdbvb]

still happening here

may you post your pipeline log?

[tintse-thxsky-MSFT]

@bdbvb @lavi09 It should be fixed now. Can you rerun the pipeline and confirm? Thankyou.

[bdbvb]

@bdbvb @lavi09 It should be fixed now. Can you rerun the pipeline and confirm? Thankyou.

I don't see any difference when re-running. Still same warning. Do I need to update anything?

[gavintoddchurch]

1.242.1 is still the task version being used. @tintse-thxsky-MSFT does there need to be a new release to get the latest changes you made?

I'm still seeing the error in my pipelines as well

[tintse-thxsky-MSFT]

@bdbvb to clarify, you are still seeing the error in both task: npm and task: npmauthenticate, correct?

Can you rerun again and paste the log in text? from line 2 to line 15 is good enough.

@gavintoddchurch sorry I was focusing on "npm authenticate" task, can you retry now? "npm" task should work now.

[bdbvb]

@bdbvb to clarify, you are still seeing the error in both task: npm and task: npmauthenticate, correct?

Can you rerun again and paste the log in text? from line 2 to line 15 is good enough.

@gavintoddchurch sorry I was focusing on "npm authenticate" task, can you retry now? "npm" task should work now.

It's working OK now, for both. Both tool versions now have lower version.

[gavintoddchurch]

Yup i'm seeing npm is using 1.238.3 now as well, and i'm not seeing the warnings. Thank you for helping us with this @tintse-thxsky-MSFT !

[anthonywhite]

still not working here

[bdbvb]

I'm getting warnings again, but this time only for npm authenticate. The task version has increased to 0.243.1

[lavi09]

@bdbvb @lavi09 It should be fixed now. Can you rerun the pipeline and confirm? Thankyou.

I still see warning in npm authenticate from today's run

[jazelenk]

Seeing this same error with UniversalPackages@0

##[warning]Can't find loc string for key: Info_GotAndMaskAuth

[shiraze]

Seeing this same error with UniversalPackages@0

##[warning]Can't find loc string for key: Info_GotAndMaskAuth

See #20203

[RickMontalvoCubero]

We started to experience the same issue with task: UniversalPackages@0 Are there any updates on this?

[shiraze]

We started to experience the same issue with task: UniversalPackages@0 Are there any updates on this?

See #20203
It is a different issue

[bdbvb]

I'm getting warnings again, but this time only for npm authenticate. The task version has increased to 0.243.1

It seems to have cleared up as of Aug 9, no more warnings (for npm or npm authenticate).

[cabralRodrigo]

Issue still present in version 1.244.1

[github-actions]

This issue is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days