Number of entries expected in End Of Central Directory does not correspond to number of entries in Central Directory

[WilliamWatterson86]

Hi,

We use this extension in our Devops to release out to Play.

This morning our extension updated to v4.273.0

Now we are getting the following error: Number of entries expected in End Of Central Directory does not correspond to number of entries in Central Directory.

2026-04-28T10:01:00.4816044Z Creating artifacts directory: D:\a\r1\a
2026-04-28T10:01:00.4920626Z Created artifacts directory: D:\a\r1\a
2026-04-28T10:01:00.4951608Z Download all required tasks.
2026-04-28T10:01:00.5043322Z Downloading task: DownloadBuildArtifacts (0.272.0)
2026-04-28T10:01:05.0544894Z Downloading task: GooglePlayRelease (4.273.0)
2026-04-28T10:01:05.6201147Z ##[error]Number of entries expected in End Of Central Directory does not correspond to number of entries in Central Directory.
2026-04-28T10:01:05.6217174Z ##[section]Finishing: Initialize job

A build ran just before the extension updated worked no problem.

How do we roll back?

[6ril]

I've been experiencing the same problem for several days.
Is a fix planned?
Unable to deploy any packages on PlayStore

[eric-taix]

What? This issue has been created on April 28th and it still on triage! Microsoft guys do you know that this issue don't let us push a new release on store?

[WilliamWatterson86]

Eric Taix (@eric-taix) Cyril Plassard (@6ril)
I had to just remove this extension altogether. My work around was to use fastlane.

1. Setup a service account as defined here: https://docs.fastlane.tools/actions/upload_to_play_store/

2. Upload the key json file you downloaded as secure file to DevOps library

3. Add a download secure file step to the pipeline which downloads your json file and gives it the output name: googlePlayJson

4. Create a new Command Line step to the release pipeline
   sudo gem install fastlane -NV

5. Add another Command Line step to the release pipeline

set -e

export FASTLANE_SKIP_UPDATE_CHECK=1

AAB_PATH="$(System.DefaultWorkingDirectory)/_[App-release package]/drop/UAT/Android/[app name].aab"
PLAY_JSON="$(googlePlayJson.secureFilePath)"

if [ ! -f "$AAB_PATH" ]; then
  echo "ERROR: AAB not found at $AAB_PATH"
  exit 1
fi

echo "Using Google Play service account JSON at $PLAY_JSON"

fastlane run upload_to_play_store \
  package_name:"[appname]" \
  aab:"$AAB_PATH" \
  track:"internal" \
  json_key:"$PLAY_JSON"

Hope this helps

[eric-taix]

Thanks WilliamWatterson86 for this workaround until the team fix this issue