Why this happens
When you look through your .xcodeproj or .xcworkspace directory in Finder, you will not find any .mobileprovision or .provisionprofile files. Xcode keeps provisioning profiles in a shared user-level directory inside ~/Library rather than inside individual project repositories.
Your project only stores references to those profiles—such as the bundle identifier, team ID, and PROVISIONING_PROFILE_SPECIFIER build setting—in project.pbxproj. When you build or archive your app, Xcode looks up the matching profile from the shared directory and copies it into the compiled app bundle.
Two things commonly make this folder hard to find:
- Hidden Library folder: macOS hides
~/Libraryby default in Finder, so browsing from your home folder will not show it. - Changed path in newer Xcode versions: Xcode 15 and earlier stored profiles in
~/Library/MobileDevice/Provisioning Profiles, whereas Xcode 16 moved them to~/Library/Developer/Xcode/UserData/Provisioning Profiles.
How to fix it
1. Open the Provisioning Profiles folder in Finder
You can jump directly to the hidden directory using Finder’s Go to Folder shortcut without changing your Finder visibility settings.
- Open Finder or click anywhere on your desktop.
- Press
Command + Shift + G(or choose Go > Go to Folder from the menu bar). - If you are using Xcode 16 or later, paste this path and press Return:
~/Library/Developer/Xcode/UserData/Provisioning Profiles
- If you are using Xcode 15 or earlier (or checking profiles left behind by an older installation), use the legacy path instead:
~/Library/MobileDevice/Provisioning Profiles
The leading ~ tells macOS to start in your current user’s home directory (/Users/<your-username>). If the folder does not exist yet, Xcode has not downloaded or installed any profiles for that version.
2. Locate and inspect profiles in Terminal
Xcode renames downloaded provisioning profiles using their UUIDs (for example, a1b2c3d4-e5f6-7890-abcd-ef1234567890.mobileprovision), which makes it difficult to tell them apart in Finder.
You can list both locations and decode a profile’s contents directly in Terminal:
# List profiles in Xcode 16+
ls -la ~/Library/Developer/Xcode/UserData/Provisioning\ Profiles
# List profiles in Xcode 15 and earlier
ls -la ~/Library/MobileDevice/Provisioning\ Profiles
Because .mobileprovision files are CMS-signed property lists, you can decode them with security cms to inspect the profile name, expiration date, team ID, and entitlements:
security cms -D -i ~/Library/Developer/Xcode/UserData/Provisioning\ Profiles/<UUID>.mobileprovision
To quickly search across all installed profiles for a specific app name or bundle identifier, loop through the folder and filter the decoded output:
for profile in ~/Library/Developer/Xcode/UserData/Provisioning\ Profiles/*.mobileprovision; do
echo "=== $profile ==="
security cms -D -i "$profile" | grep -A 1 -E "Name|application-identifier|ExpirationDate"
done
If you are checking an older Xcode installation, replace the path in the for loop with ~/Library/MobileDevice/Provisioning\ Profiles/*.mobileprovision.
3. Download and verify profiles inside Xcode
If the folder is empty or missing a newly created profile from the Apple Developer portal, pull the latest profiles directly through Xcode:
- Open Xcode and go to Xcode > Settings (or Preferences on older versions).
- Select the Accounts tab.
- Choose your Apple ID on the left and your team on the right.
- Click Download Manual Profiles.
To confirm which profile a specific target is using, open your project, select the target, and go to the Signing & Capabilities tab. Click the info icon (i) next to Provisioning Profile to view the active profile’s name, expiration date, and included capabilities.
4. Inspect the embedded profile inside a built app
When troubleshooting a distribution or device-installation error, you may need to verify the exact profile that was bundled into an .app or .xcarchive rather than the ones sitting in ~/Library.
Xcode copies the active profile into the compiled bundle as embedded.mobileprovision (for iOS, iPadOS, watchOS, and tvOS) or embedded.provisionprofile (for macOS). You can inspect it with security cms:
# Inspect an iOS .app bundle inside an xcarchive
security cms -D -i /path/to/MyApp.xcarchive/Products/Applications/MyApp.app/embedded.mobileprovision
If you have an .ipa file, rename or unzip it (unzip MyApp.ipa) and run the same command against Payload/MyApp.app/embedded.mobileprovision.
How to prevent it
- Use automatic signing when possible: Keeping Automatically manage signing enabled in Signing & Capabilities lets Xcode create, renew, and store profiles without manual file management.
- Sync through Xcode Settings: Use Xcode > Settings > Accounts > Download Manual Profiles instead of manually copying
.mobileprovisionfiles into~/Library. - Clean up expired profiles: Periodically remove expired profiles from your Provisioning Profiles folder so manual signing does not pick up stale configurations.
- Check both paths in CI/CD scripts: If your build automation installs or cleans provisioning profiles, check the Xcode version or inspect both
~/Library/Developer/Xcode/UserData/Provisioning Profilesand~/Library/MobileDevice/Provisioning Profiles.
FAQ
Are Xcode provisioning profiles stored inside my project folder?
No. Xcode stores provisioning profiles in a shared ~/Library directory on your Mac and only saves references to them in your project settings. When you build or archive the app, Xcode embeds a copy of the matching profile inside the compiled .app bundle.
Why are provisioning profile filenames random UUIDs?
Xcode names each file using the profile’s unique UUID key so multiple versions of a profile with the same name can coexist without overwriting one another. You can read the human-readable profile name inside the file by running security cms -D -i <file> in Terminal.
Is it safe to delete all files in the Provisioning Profiles folder?
Yes, as long as your profiles are still available in your Apple Developer account. Deleting the files clears out stale or expired profiles, and Xcode will re-download active ones the next time you build with automatic signing or click Download Manual Profiles in Xcode > Settings > Accounts.
Parts of this guide are adapted from content licensed under CC BY-SA 4.0; this article is shared under the same license.
