GooglePlayRelease@4.276.0 fails with ERR_REQUIRE_ESM from html-encoding-sniffer

[hamaro9]

After the Google Play Azure DevOps extension updated to 4.276.0, our pipeline started failing immediately in the GooglePlayRelease@4 task.

The task fails before authenticating or uploading the AAB.

Environment

• Azure DevOps Google Play extension version: 4.276.0
• Task: GooglePlayRelease@4
• Agent type: self-hosted Windows agent
• Agent version: 4.255.0
• Agent OS: Windows
• Pipeline pool: self-hosted Windows VM

Error

Starting: Publish AAB to Google Play Internal Track
==============================================================================
Task         : Google Play - Release
Description  : Release an app to the Google Play Store
Version      : 4.276.0
Author       : Microsoft Corporation
Help         : https://marketplace.visualstudio.com/items?itemName=ms-vsclient.google-play
==============================================================================
##[error]Unhandled: require() of ES Module C:\agent\_work\_tasks\GooglePlayRelease_...\4.276.0\node_modules\@exodus\bytes\encoding-lite.js from C:\agent\_work\_tasks\GooglePlayRelease_...\4.276.0\node_modules\html-encoding-sniffer\lib\html-encoding-sniffer.js not supported.
Instead change the require of encoding-lite.js in C:\agent\_work\_tasks\GooglePlayRelease_...\4.276.0\node_modules\html-encoding-sniffer\lib\html-encoding-sniffer.js to a dynamic import() which is available in all CommonJS modules.
##[error]Error [ERR_REQUIRE_ESM]: require() of ES Module C:\agent\_work\_tasks\GooglePlayRelease_...\4.276.0\node_modules\@exodus\bytes\encoding-lite.js from C:\agent\_work\_tasks\GooglePlayRelease_...\4.276.0\node_modules\html-encoding-sniffer\lib\html-encoding-sniffer.js not supported.
    at Object.<anonymous> (C:\agent\_work\_tasks\GooglePlayRelease_...\4.276.0\node_modules\html-encoding-sniffer\lib\html-encoding-sniffer.js:2:41)
Finishing: Publish AAB to Google Play Internal Track

Expected behavior

GooglePlayRelease@4 should load successfully and upload the AAB to the configured Google Play track.

Actual behavior

The task crashes while loading its bundled Node dependencies, before upload starts.

[SaebAmini]

Had the same issue. Updating the agent from version 4.258.1 to the latest version (5.275.0) through Azure DevOps resolved it.

[SonaV]

We can confirm this issue.

Environment:

• Azure DevOps Server (on-premises)
• macOS self-hosted agent
• Google Play extension 4.276.0

After upgrading from 4.273.0 to 4.276.0, all Google Play Release tasks started failing with the same ERR_REQUIRE_ESM error before connecting to Google Play.

The same pipeline worked correctly with version 4.273.0.

We were able to work around the problem by applying a local patch to the task files, which confirms this is a regression introduced in version 4.276.0 rather than a pipeline or configuration issue.

[PierreAubeuf]

We encountered the same issue.

Using the latest release of azure pipelines agent (version 4.274.1 / May 27) also resolves the problem, so there is no need to force the installation of a pre-release.

[milesrush-pace]

Had the same problem after the server upgraded the task from 4.273.0 to 4.276.0. I was able to work around it by downgrading jsdom in the cached task folder on the agent machine.

[beeradmoore]

Updating two agents (v4.252.0 and v4.274.1) to v5.275.0 fixed the issue for me.

[milesrush-pace]

Updating two agents (v4.252.0 and v4.274.1) to v5.275.0 fixed the issue for me.

Where did you find v5.275.0? All I see on marketplace is v4.276.0.

[vijayardhani]

This is how you can fix this issue

login to the machine/server and run:_

1. cd /Users/careington/agent/_work/_tasks/GooglePlayRelease_8cf7cac0-620b-11e5-b4cf-8565e60f4d27/4.276.0
2. npm install jsdom@22.1.0 --save-exact

[beeradmoore]

milesrush-pace , we use self hosted agents in Azure Pipelines. I went to the page to see what agents are online in org settings, hit 3 dots, hit update agent.

Unsure if the new agents happened to come with new node packages which is what other people are updating or what but that is what did it for me.

[milesrush-pace]

@milesrush-pace , we use self hosted agents in Azure Pipelines. I went to the page to see what agents are online in org settings, hit 3 dots, hit update agent.

Unsure if the new agents happened to come with new node packages which is what other people are updating or what but that is what did it for me.

I misread your original post. I see what you mean now. Thanks for clarifying.