Closed MatthewSteeples closed 2 years ago
I tested https://azurecliprod.blob.core.windows.net/msi/azure-cli-2.17.0.msi on a local machine and it installs correctly.
I found the the same issue has been mentioned multiple times:
We didn't make any changes to the MSI packaging pipeline recently.
While we are doing more research from CLI side, do you mind reaching out to the customer support of Microsoft Endpoint Manager as well? Thanks a lot.
Hi @jiasli,
Thanks for the response. I'll raise a ticket and see what happens. I tried uploading the 2.16 version into the portal and that still works fine, so there's definitely something unusual going on
Support ticket opened - # 23514049
This problem still exists with 2.18. I'm still jumping through the various hoops with the service request
Sadly the best I could get out of support was "Yes we can reproduce the problem, let us know if you fix it"
Same here with 2.18. confirmed.
Hi @MatthewSteeples, I am not sure what app id
means in the error message. Could you provide this issue to the support team or add me to the email communication? My email address is
Hi @jiasli I'm not sure what it means either, but it's all the portal reveals. Support closed my case (as I didn't have time to go through the steps that the should have been doing).
I'll forward you the emails I have from them.
Problem still exists for 2.20
Just noticed that the Azure Portal gives me this error:
_1rRA0vmyWGo.js:10 [fx] 11:00:07 PM MsPortalImpl/Services/Services.IntuneAppParse Services.IntuneAppParse: [IntuneAppParse] Error parsing .msi file with code: 6
@jiasli is that something you can pass on to the right team?
@MatthewSteeples, thanks for the information. We are internally working with Intune team on this. We will let you once there is any updates.
Early indications suggest that this is fixed in 2.21 (or in the portal)
This has been working fine for us for a while now
Describe the bug We use Microsoft Endpoint Manager to deploy Azure CLI to our dev machines. Each release has been fine to do an in-place upgrade apart from 2.17. When trying to upload 2.17 to the portal an error is displayed
The selected app package does not appear to have an app id.
To Reproduce
Expected behavior Application is uploaded and available to deploy
Environment summary MSI install