Adding an Entitlements.plist breaks the iOS project

[marwalsch]

Description

Adding an Entitlements.plist into the iOS subdirectory causes the project build to fail with a "Could not find any available provisioning profiles for {project} on iOS." error for some reason. Removing it results in success.
It's also unclear whether resolving the bundle for secure access works through the same notation as in Xamarin.

<key>keychain-access-groups</key>
	<array>
		<string>$(AppIdentifierPrefix)$(CFBundleIdentifier)</string>
	</array>

Steps to Reproduce

1. Create an empty MAUI project;
2. Create an Entitlements.plist inside the iOS directory.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>

</dict>
</plist>

3. Witness the build fail as it is present.

Version with bug

Preview 10 (current)

Last version that worked well

Unknown/Other

Affected platforms

iOS

Affected platform versions

Latest releases shipped with VS2022 Preview 1.1

Did you find any workaround?

No response

Relevant log output

No response

[shimingsg]

Verified Repro with iPhone 13 IOs 15.2. Repro project
3715.zip

[mattleibow]

Moving this to a feature/enhancement because the presence of an entitlement involves signing the app package. However, maybe the rules need to change to maybe first check the signing before actually adding the entitlements. However, this may result in unexpected behaviour as trying to make use of features enabled by the entitlements may not work if the app is not signed.

[Mephisztoe]

because the presence of an entitlement involves signing the app package

Just wondering:
You only need to add entitlements when the app needs them (like when configuring an app for receiving Push Notifications). In this case, it is mandatory to also create a manual provisioning profile that corresponds to these entitlements and have this profile installed on the Mac so that Visual Studio can pull it.

However, Visual Studio is per default configured for automatic provisioning and there is still no dialog for setting this up in an easy way. Maybe @marwalsch only needs to switch to manual provisioning (by adding manual to the project file) and configure both the code signing certificate and a matching provisioning profile for the respective build target...?

[ghost]

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

[janwiebe-jump]

Hi @marwalsch
I ran into this issue as well.
I got it working,by manually editing the csproj file, and fixing the CodesignEntitlements key from

<CodesignEntitlements>Entitlements.plist</CodesignEntitlements>

to

<CodesignEntitlements>Platforms\iOS\Entitlements.plist</CodesignEntitlements>

[marwalsch]

@janwiebe-jump Thanks for the suggestion.

This has apparently become a non-issue on latest MAUI builds and Visual Studio versions, thus I am closing.