Hello @Kim Strasser !
The identity used to sign the executable is no longer valid.
Your app bundle was signed with a certificate or provisioning profile that your iPad no longer accepts. Since you recently renewed your Apple Developer membership and added a new device, your old signing setup is now out of sync. Here are the steps to fix that you can try:
Refresh Certificates and Profiles
- Go to Apple Developer Certificates, Identifiers & Profiles.
- Check your iOS Development certificate:
- If it’s expiring soon, revoke it and create a new one.
- Download the new
.cerand install it in your Mac’s Keychain.
- Recreate or update your Provisioning Profile:
- Make sure your new iPad Air is included in the profile’s device list.
- Download the updated
.mobileprovisionfile.
Sync with Visual Studio
- In Visual Studio for Mac/Windows:
- Go to Tools → Options → Xamarin → Apple Accounts.
- Select your Apple ID → View Details.
- Click Refresh to pull the latest certificates and profiles.
- If your new certificate doesn’t appear, import it manually from Keychain (export as
.p12with private key, then import into VS).
Clean and Rebuild
- Delete the app from your iPad.
- In your project folder, delete
bin/andobj/directories. - Rebuild the project so it signs with the refreshed identity.
Verify Signing Settings
- In your iOS project properties:
- Under iOS Bundle Signing, ensure:
- Signing Identity = iOS Developer (new certificate).
- Provisioning Profile = the updated one with your iPad included.
- Under iOS Bundle Signing, ensure:
- If you use Automatic Provisioning, make sure your Apple ID is signed in and let VS handle it.
- If you use Manual Provisioning, explicitly select the new profile.
Visual Studio should be able to deploy again.
Hope you fix this issue to proceed your work!