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
It doesn't really help you when you're facing trouble with the signing capabilities and adhoc/appstore mobile provisioning file.
Let me explain myself.
In XCode, i have two configurations under "Signing and Capabilities".
First one is debug, using a provisioning profile created using Ad hoc type
Second one is release, using a provisioning profile created using App store type
In my AppCenter configuration, in branch configuration.
For my develop branch, i set my ad hoc provisioning profile.
For my master branch, i set my release provisioning profile.
However, it doesn't seems like i can choose which Signing capabilities configuration it is going to be built with
So i'm facing the issue that i'm building an app on my develop branch, using ad hoc provisioning profile, and still it cannot be installed on my testers devices, because it seems like it is always using the "Release type" configuration defined in XCode
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
ID: 1b3efbfa-b70b-9039-4b49-6ba4ce6c36af
Version Independent ID: 73e079aa-bbc3-2a06-a5d1-c4827bd5e3dc
It doesn't really help you when you're facing trouble with the signing capabilities and adhoc/appstore mobile provisioning file.
Let me explain myself.
In XCode, i have two configurations under "Signing and Capabilities".
In my AppCenter configuration, in branch configuration.
For my
develop
branch, i set my ad hoc provisioning profile.For my
master
branch, i set my release provisioning profile.However, it doesn't seems like i can choose which Signing capabilities configuration it is going to be built with
So i'm facing the issue that i'm building an app on my develop branch, using ad hoc provisioning profile, and still it cannot be installed on my testers devices, because it seems like it is always using the "Release type" configuration defined in XCode
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: