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: powerapps-docs/maker/common/wrap/create-key-vault-for-code-signing.md
+10-3Lines changed: 10 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -205,7 +205,7 @@ The following Azure key vault errors might appear in wrap for Power Apps and can
205
205
206
206
- Add a new **Tag** for your **Android Certificate**.
207
207
1. The **Tag name** should be based on the **bundle id** that you used in your **wrap project**. For example, if the **bundle id** for your wrapped app is **com.testApp.wrap**, then the new **Tag name** should be **com.testApp.wrap.keystore**.
208
-
2. The **Tag value** should correspod to the name you chose for your **Certificate** when uploading a certificate file in the previous step. For example, if your **Android cerfificate** is named **AndroidWrapCertificate**, then the value for the **Tag value** should also be **AndroidWrapCertificate**.
208
+
2. The **Tag value** should correspod to the name you chose for your **Certificate** when uploading a certificate file in the previous step. For example, if your **Cerfificate** is named **AndroidWrapCertificate**, then the value for the **Tag value** should also be **AndroidWrapCertificate**.
209
209
210
210
> [!div class="mx-imgBorder"]
211
211
> 
@@ -225,8 +225,8 @@ The following Azure key vault errors might appear in wrap for Power Apps and can
225
225
> 
226
226
227
227
- Add a new **Tag** for your **iOS Certificate**.
228
-
-1. The **Tag name** should be based on the **bundle id** that you used in your **wrap project**. For example, if the **bundle id** for your wrapped app is **com.testApp.wrap**, then the new **Tag name** should be **com.testApp.wrap.cert**.
229
-
2. The **Tag value** should correspod to the name you chose for your **Certificate** when uploading a certificate file in the previous step. For example, if your **iOS Cerfificate** is named **iOSCertificate1**, then the value for the **Tag value** should also be **iOSCertificate1**.
228
+
1. The **Tag name** should be based on the **bundle id** that you used in your **wrap project**. For example, if the **bundle id** for your wrapped app is **com.testApp.wrap**, then the new **Tag name** should be **com.testApp.wrap.cert**.
229
+
2. The **Tag value** should correspod to the name you chose for your **Certificate** when uploading a certificate file in the previous step. For example, if your **Cerfificate** is named **iOSCertificate1**, then the value for the **Tag value** should also be **iOSCertificate1**.
230
230
231
231
> [!div class="mx-imgBorder"]
232
232
> 
@@ -237,5 +237,12 @@ The following Azure key vault errors might appear in wrap for Power Apps and can
237
237
| ------------- |:-------------:|
238
238
|1000123 | iOS profile is not valid|
239
239
240
+
- Import your **Provisioning Profile** as a **Secret**
241
+
- Add a new **Tag** for your **Provisioning Profile**.
242
+
-1. The **Tag name** should be based on the **bundle id** that you used in your **wrap project**. For example, if the **bundle id** for your wrapped app is **com.testApp.wrap**, then the new **Tag name** should be **com.testApp.wrap.profile**.
243
+
2. The **Tag value** should correspod to the name you chose for your **Secret** when uploading a povisioning profile in the previous step. For example, if your **Secret** is named **iOSProvisioningProfileSecret**, then the value for the **Tag value** should also be **iOSProvisioningProfileSecret**.
244
+
245
+
> [!div class="mx-imgBorder"]
246
+
> 
0 commit comments