A provisioning profile is an essential component in iOS development that allows your app to run on a physical device during testing or to be distributed for beta testing or App Store distribution.
The error “provisioning profile doesn’t include the currently selected device” occurs when you try to run an app on a device that is not included in the provisioning profile associated with the app. This situation can happen for a few reasons:
-
New device: If you have recently added a new device to your account, you need to update your provisioning profile to include that device. To do so, you can either edit the existing provisioning profile or create a new one.
Example:
Let’s say you have been testing your app on an iPhone 11 and recently obtained an iPhone 12 for testing. You’ll need to update your provisioning profile to include the iPhone 12’s unique identifier (UDID) so that you can run the app on that device. -
Expired profile: Provisioning profiles have an expiration date, and if your profile has expired, it won’t allow you to run the app on any devices. In that case, you need to generate a new provisioning profile.
Example:
Let’s say you created a provisioning profile six months ago, and it had a validity period of three months. After the expiration date, the profile becomes invalid, and you’ll need to create a new one to continue testing on devices. -
Wrong profile: Sometimes, due to configuration issues or mistakes, you may be using the wrong provisioning profile. This error can occur if you accidentally select a provisioning profile that doesn’t match the device you are trying to run the app on.
Example:
Suppose you have two provisioning profiles, one for development and another for distribution. If you mistakenly use the distribution profile to test the app on a physical device, it will result in the mentioned error since the distribution profile does not include any devices for testing purposes.
To resolve the error, you need to make sure that your provisioning profile is up-to-date, includes the correct device, and is the appropriate profile for the purpose of testing or distribution. Additionally, ensure that the provisioning profile is properly configured in your Xcode project settings.
- Property ‘checked’ does not exist on type ‘htmlelement’
- Protobuf compiler version doesn’t match library version
- Powershell write-host bold
- Property ‘exact’ does not exist on type ‘intrinsicattributes & routeprops’.
- Packagesnotfounderror: the following packages are missing from the target environment: – tensorflow
- Property id does not exist on this collection instance. laravel
- Property would not be serialized into a ‘parcel’
- Provider.js:24 uncaught typeerror: cannot read properties of undefined (reading ‘getstate’)