DevOps build pipeline, for Xamarin.iOS Could not find any available provisioning profiles

Question

I'm trying to setup a DevOps build pipeline (eventually for UI Testing) initially for Xamarin.iOS. We have other issues with AppCenter.

I've used the default Xamarin iOS template and am working through the issues.

We're using a mac vm / image.

We decided to use a Debug version of our app as this would provide more useful information from any UI Tests errors. So eventually we can test our build on Simulators in AppCenter.

However, I'm getting this error. I've ensured that I've included a entitlements.plist which has APS Environment set to development . I'm just unsure why it would need a provisioning profile.

I'm not actually sure what AppCenter would require from the build, perhaps it only works with ipa files? And that therefore requires a profile???

(_DetectSigningIdentity target) -> 
  /Library/Frameworks/Mono.framework/External/xbuild/Xamarin/iOS/Xamarin.Shared.targets(239,3): 
error : Could not find any available provisioning profiles for ourapp.iOS on iOS. 
[/Users/runner/work/1/s/ourapp/iOS/ourapp.iOS.csproj]
/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/iOS/Xamarin.Shared.targets(239,3): 
error : [/Users/runner/work/1/s/ourapp/iOS/ourapp.iOS.csproj]

Answer 1

If the project include Entitlements.plist, you will need provisioning profile to enable entitlements. See threads here and here .

As it explained as below. If APS Environment is set to development. It means you need togenerate a development provisioning profile. See here .

Xcode sets the value of the entitlement based on your app's current provisioning profile. For example, if you're using a development provisioning profile, Xcode sets the value to development.

You can check the document Device provisioning for Xamarin.iOS to generate a provisioning profile. Also see this thread .

When you get your provisioning profile. You can upload it to azure develops secure files . And use InstallAppleProvisioningProfile task to download it in your pipeline. See document here for more information. You can also check out the example in this blog .