Hi Angelina Souy,
Thanks for bringing your issue. This issue you are facing is due to a regression introduced in Azure CLI version 2.77, specifically affecting the az batch application package create command.
In this version, when executing the command, it tries to upload the application package blob but does not handle existing blobs correctly. Even when providing a new version name, instead of uploading the actual zip file content, it mistakenly uploads just the file path as a string rather than the file itself.
I have found that this regression issue tracked in Azure CLI GitHub repository three days ago.
https://github.com/Azure/azure-cli/issues/32086
As a workaround we recommend you to:
Use Azure REST API or the Azure Batch SDK to upload application packages.
Use an older Azure CLI version (e.g., 2.76) where this command works as expected.
Please refer official release notes of Azure CLI version 2.77 September version: https://free.blessedness.top/en-us/cli/azure/release-notes-azure-cli?view=azure-cli-latest
Please let me know if you have any other queries.
If the answer is helpful, please click "Accept Answer" and "Upvote it."