I am completely blocked by the 0xe8008015 error when deploying a .NET MAUI application to a local iPhone via Hot Restart (VS 2022 on Windows).
I am not using an old project. I have performed a complete “scorched earth” reset to build this from a 100% clean slate, but the problem persists.
Steps Taken
To ensure no “ghost” settings (from old accounts or builds) could interfere, I did the following in this exact order on Apple Portal:
-
Users & Access: Deleted all old API Keys. Created a brand new “Admin” API Key (.p8 file).
-
Devices: Deleted all old/duplicate test devices. Re-added my two iPhones (iPhone 13 and iPhone 14) using their UDIDs. The device list is now 100% clean.
-
Certificates: Revoked and Deleted all “Development” certificates.
-
Profiles: Deleted all “iOS App Development” profiles.
-
Identifiers: Deleted the old App ID. Created a brand new Identifier (com.example.newapp.mobile) explicitly tied to my Business Account Team ID.
On Local Machine:
-
Deleted bin, obj, and .vs folders.
-
Cleaned the .csproj file of all CodesignKey or CodesignProvision groups.
-
Emptied %LOCALAPPDATA%\Xamarin\iOS\ (both Provisioning and Certificates folders).
-
Emptied TEMP\Xamarin.
-
Restarted the PC.
The Known Facts of This Setup
-
Forced Capability: When creating the new App ID (Step 5), my Apple Business Account forces the “In-App Purchase” (IAP) capability on. It is checked and locked, it cannot be disabled.
-
My App ID Capabilities: I enabled Push Notifications and (was forced to accept) In-App Purchase. I explicitly disabled Mac Catalyst.
-
My Entitlements.plist: To match the App ID, my Entitlements.plist correctly declares these two capabilities:
XAML:
aps-environment
development
com.apple.developer.in-app-purchase
What Happens on First Deploy (The Failure)
I open VS (as Admin).
I go to Tools > Options > Xamarin > Apple Accounts and successfully add my new “Admin” API Key (.p8 file, Key ID, Issuer ID).
I open the project, set iOS Bundle Signing to “Automatic Provisioning” and select my (only) Team.
I hit Deploy.
-
“Automatic Provisioning” successfully creates a new, “Valid” Development Certificate on the Portal. (This is confirmed in the View Details… window in VS).
-
“Automatic Provisioning” also creates a new Provisioning Profile (VS: com.example.newapp.mobile Development).
The build fails with 0xe8008015 (A valid provisioning profile for this executable was not found.).
This same error happens on two different, clean iPhones (iPhone 13 and iPhone 14).
A Suspicious Detail (But Not a Proven Cause)
While investigating, I noticed a strange mismatch (which may or may not be the cause of the error):
My App ID (in the Portal) was created without Mac Catalyst enabled.
However, the auto-generated VS:… profile does have “Include Mac Devices” enabled when I inspect it on the Portal.
I am not sure if this is the cause of the 0xe8008015 error, or just a harmless bug in Visual Studio’s auto-profiler. It does, however, suggest that the auto-profiler might not be correctly reading the App ID’s capabilities.
My Questions:
Is this a known bug with Automatic Provisioning when a Business Account forces In-App Purchase?
Is there a step I’m missing in this 100% “Fresh Start” scenario that could still cause 0xe8008015?
Has anyone found that the only solution is to abandon “Automatic Provisioning” and use “Manual Provisioning” in this specific scenario (Forced IAP)?
Thank you.
