Why this happens
The application could not be verified means the iPhone rejected the app during installation verification. When the same project installs on one device but fails on another, compare the devices’ existing app installations and provisioning eligibility before changing application code.
One cause is an existing installation with the same bundle identifier that cannot be replaced by the development build under its current signing configuration. That installed copy might have come from the App Store, a previous development build, or a different signing team. Sharing a bundle identifier is normal for app updates; the problem is an incompatible replacement, not the identifier alone.
The original report involved Xcode 6.1 and an iPhone updated to iOS 8.1.3. The highest-rated solution was to delete the installed app, restart Xcode, and deploy again. Another answer specifically traced the failure to an App Store copy already on the phone. Those reports support checking the installed app first, but they do not establish that every verification failure has the same cause.
How to fix it
1. Protect local data before removing the installed app
Deleting the app is the most direct fix reported for this symptom, but it can remove the app’s local documents, databases, preferences, and other sandbox data.
Before proceeding:
- Identify the installed app that corresponds to your Xcode target.
- Check whether it contains anything you need to keep.
- Use the app’s export or synchronization features where available.
- If it is a development installation, consider downloading its container through Xcode’s Devices and Simulators window before deleting it.
Downloading a container is useful for inspection and recovery planning, but do not assume every container can be restored into every differently signed build. For important information, prefer an export format or synchronization method the app explicitly supports.
If this is your everyday App Store installation and you cannot safely lose its local data, skip deletion for now and consider a separate development bundle identifier in step 5.
2. Delete the existing copy, restart Xcode, and reinstall
Once the data is protected:
- On the affected iPhone, delete the installed app. Choose Delete App, not merely removal from the Home Screen.
- Quit Xcode and reopen the project or workspace.
- Select the affected iPhone as the run destination.
- Build and run the app again.
This follows the highest-rated solution from the source discussion. Restarting Xcode was part of that reported fix, although the report did not isolate whether restarting or deleting the app made the difference.
Removing the existing installation eliminates the need to replace that particular installed copy. If the new installation succeeds, an incompatibility with the previous installation is a strong lead.
Do not treat this as proof that installing over an App Store app always fails. Compatible app updates are expected to reuse their bundle identifier. The useful distinction is whether this development build is permitted to replace the specific copy already on the device.
If the phone has no existing copy, or deletion does not help, continue with signing and provisioning checks rather than repeatedly reinstalling.
3. Confirm the target’s bundle identifier and signing team
In Xcode, select the project, select the application target, and open Signing & Capabilities.
Check these items:
- Bundle Identifier: Confirm that you are building the intended app rather than another target or configuration.
- Team: Select the development team that should sign this build.
- Signing status: Resolve any signing or provisioning errors Xcode displays.
- Build configuration: Check the configuration used by the scheme’s Run action, especially if Debug and Release use different signing settings.
A project can contain several targets with similar names, so verify the actual application target used by the selected scheme. If the app includes extensions, review their signing settings as well; they also need valid signing arrangements.
With automatic signing, allow Xcode to manage the required development signing assets after selecting the correct team. With manual signing, verify the selected profile and signing certificate yourself.
Avoid changing unrelated settings simply because another device works. A working device is useful evidence, but it does not prove that every device is eligible under the profile used for the failing installation.
4. Verify the profile actually used by the build includes the iPhone
The source question stated that all device UDIDs had been added to a provisioning profile. That is worth checking, but it leaves a second question: is the build using a profile that contains those devices?
For a development installation on a physical iPhone, check that:
- The affected device is registered with the intended developer team.
- The development provisioning profile includes that device.
- The profile matches the app’s identifier and required capabilities.
- Xcode is using the updated profile rather than an older one.
With manual signing, adding a device to the developer account does not update a profile already embedded in a previously built app. Update or regenerate the profile as necessary, make it available to Xcode, select it for the relevant configuration, and rebuild.
With automatic signing, inspect any errors Xcode reports instead of assuming registration completed successfully. Account access and team permissions can affect whether Xcode can manage signing assets.
Retry installation after correcting the profile. If it still fails, expand the installation error details in Xcode and look for a more specific signing or provisioning message. The short verification message alone is not enough to identify every underlying failure.
5. Use a separate development identifier when both copies must remain
If you need to keep the App Store app installed while developing, a separate bundle identifier is often a better workflow than deleting the production copy repeatedly.
For example:
Production: com.example.reader
Development: com.example.reader.dev
Configure the development target or build configuration to use the development identifier and valid signing assets for it. Giving the development app a distinct display name also makes it easier to recognize on the Home Screen.
This is not just a cosmetic change. Services associated with the app’s identity may need corresponding configuration, including push notifications, App Groups, keychain sharing, and backend integrations. Review those dependencies before adopting the separate identifier.
Use this approach for side-by-side development. It does not test replacement of the production app, and the two installations do not automatically share their local data.
How to prevent it
- Keep track of whether each test device has an App Store, development, or other distributed copy installed.
- Use a distinct development bundle identifier when you need production and development copies side by side.
- Keep the signing team and bundle identifier intentional across targets and build configurations.
- After adding a device, confirm that the provisioning profile used by the next build includes it.
- Preserve important local data before troubleshooting by deletion.
- Test app-update behavior separately from fresh-install behavior; success in one does not establish success in the other.
FAQ
Why does the app install on one iPhone but not another?
The devices may have different existing copies of the app, or only one may be included in the provisioning profile used by the build. Compare those conditions first rather than assuming the source code or the iPhone model is responsible.
Must I delete the App Store version to run my development build?
Not universally. In the source discussion, deleting the App Store copy resolved the failure for one developer, but the important issue is whether the development build can replace the installed app under its signing configuration. A separate development bundle identifier avoids replacing it at all.
Did an iOS update cause the verification error?
The original report appeared after an update to iOS 8.1.3, but that timing does not establish the underlying cause. Check the installed app, signing settings, and device provisioning before attributing the failure to an operating-system bug.
Parts of this guide are adapted from content licensed under CC BY-SA 3.0; this article is shared under the same license.
