InstallAppleProvisioningProfileV1 has started failing with a Mac provisioning file

[kevcrooks]

Bug
Task: InstallAppleProvisioningProfileV1

This task used to work for us until yesterday, and it's started failing with the error:
##[error]Error: Provisioning profile file should have the extension '.mobileprovision'

We need to install a provisioning profile for Xamarin.Mac, and the file downloaded from Apple has the extension *.provisionprofile, but the Pre-job step in the task has started failing yesterday with the error above. (This would be ok if we were using a mobile provisioning profile, but we need to use a Mac one, which seems to have a different extension).

Is there a work-around or fix available for this?

Server - Azure Pipelines
Agent - Hosted

Full log for the step:
2020-06-11T08:02:16.3949460Z ##[section]Starting: Install provisioning: Release 2020-06-11T08:02:16.4183890Z ============================================================================== 2020-06-11T08:02:16.4185030Z Task : Install Apple provisioning profile 2020-06-11T08:02:16.4185950Z Description : Install an Apple provisioning profile required to build on a macOS agent machine 2020-06-11T08:02:16.4186370Z Version : 1.170.1 2020-06-11T08:02:16.4187090Z Author : Microsoft Corporation 2020-06-11T08:02:16.4188100Z Help : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/install-apple-provisioning-profile 2020-06-11T08:02:16.4188580Z ============================================================================== 2020-06-11T08:02:18.5007270Z ##[error]Error: Provisioning profile file should have the extension '.mobileprovision' 2020-06-11T08:02:18.5065050Z ##[section]Finishing: Install provisioning: Release

[kevcrooks]

It looks like the latest change to this task (e184c0a5c4ca73c836da9f57374f392b94e9727a) should have fixed the issue we're seeing - is it a case of waiting for the update to be rolled out, or can do something on our end to get the latest version?

[anatolybolshakov]

Hi @kevcrooks!
Yes, it's going to be rolled out, but at the moment you can follow these steps to upload fixed version to your organization #13046 (comment)

[anatolybolshakov]

Hi @kevcrooks, fix was already merged for this issue - I'm closing this issue at the moment, please feel free to reopen if issue still appears for you