You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/ios/device-provisioning/manual-provisioning.md
+44-1Lines changed: 44 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: "Manual provisioning for .NET MAUI iOS apps"
3
3
description: "Learn how to use manual provisioning to create development certificates and profiles for .NET MAUI iOS apps."
4
-
ms.date: 11/25/2024
4
+
ms.date: 12/12/2024
5
5
ms.custom: sfi-image-nochange
6
6
---
7
7
@@ -119,6 +119,12 @@ The provisioning profiles will be downloaded on Windows, and exported to your Ma
119
119
# [Visual Studio Code](#tab/visual-studio-code)
120
120
<!-- markdownlint-enable MD025 -->
121
121
122
+
Follow the instructions for .NET CLI.
123
+
124
+
<!-- markdownlint-disable MD025 -->
125
+
# [.NET CLI](#tab/cli)
126
+
<!-- markdownlint-enable MD025 -->
127
+
122
128
After creating a development provisioning profile in your Apple Developer Account, you will need to download it in Xcode so that it's available for signing your app:
123
129
124
130
1. Open the **Xcode** app.
@@ -132,6 +138,10 @@ After creating a development provisioning profile in your Apple Developer Accoun
132
138
133
139
## Enable manual provisioning
134
140
141
+
<!-- markdownlint-disable MD025 -->
142
+
# [Visual Studio](#tab/vswin)
143
+
<!-- markdownlint-enable MD025 -->
144
+
135
145
After manually creating the development provisioning profile, and installing it in Visual Studio, your .NET MAUI app project should be configured to use manual provisioning:
136
146
137
147
1. In **Solution Explorer** right-click on your .NET MAUI app project and select **Properties**. Then, navigate to the **MAUI Shared > General** tab and ensure that the value of the **Application ID** field corresponds to the format of the App ID you created earlier.
@@ -141,6 +151,39 @@ After manually creating the development provisioning profile, and installing it
141
151
142
152
1. In the **Bundle Signing** properties, select your **Signing identity** and **Provisioning profile**, or set both to **Automatic**. When **Signing identity** and **Provisioning profile** are both set to **Automatic**, Visual Studio will select the signing identity and provisioning profile based on the **Bundle identifier** in **Info.plist** (which is identical to the value of the **Application ID** property in your project file).
143
153
154
+
<!-- markdownlint-disable MD025 -->
155
+
# [Visual Studio Code](#tab/visual-studio-code)
156
+
<!-- markdownlint-enable MD025 -->
157
+
158
+
Follow the instructions for .NET CLI.
159
+
160
+
<!-- markdownlint-disable MD025 -->
161
+
# [.NET CLI](#tab/cli)
162
+
<!-- markdownlint-enable MD025 -->
163
+
164
+
After manually creating the development provisioning profile and downloading it, your .NET MAUI app project should be configured to use manual provisioning by setting the appropriate properties in your project file.
165
+
166
+
By default, if the `CodesignKey` and `CodesignProvision` properties are not set in your project file, the build will automatically select the appropriate certificate and provisioning profile. However, if the automatic selection is incorrect for your scenario, you can explicitly specify these properties:
167
+
168
+
1. Ensure that the `<ApplicationId>` property in your project file corresponds to the format of the App ID you created earlier.
169
+
1. Add the following properties to a `<PropertyGroup>` in your project file (*.csproj):
170
+
171
+
```xml
172
+
<PropertyGroup>
173
+
<CodesignKey>Apple Development: Your Name (ABCDEFGH)</CodesignKey>
Replace `Apple Development: Your Name (ABCDEFGH)` with the exact name of your signing certificate as it appears in Keychain Access, and `My Provisioning Profile` with the exact name of your provisioning profile.
179
+
180
+
> [!TIP]
181
+
> To find your signing certificate name, open **Keychain Access** on your Mac and look in the **My Certificates** category. To find your provisioning profile name, check the name you assigned when creating the profile in your Apple Developer Account.
182
+
183
+
For more information about these properties, see [CodesignKey](/dotnet/ios/building-apps/build-properties#codesignkey) and [CodesignProvision](/dotnet/ios/building-apps/build-properties#codesignprovision).
184
+
185
+
---
186
+
144
187
[!INCLUDE [Deploy the app to your device](~/ios/includes/deploy.md)]
0 commit comments