Windows端Visual Studio 2017中安装Xamarin.Forms iOS描述文件的方法

Hey there, I’ve helped folks work through this exact scenario before—let’s get your .mobileprovision certificate sorted so you can start receiving push notifications via Urban Airship. Here’s a step-by-step breakdown tailored to your setup:

1. First: Install the .mobileprovision on Your Remote Mac #

Even though you’re coding on Windows, the remote Mac handles all iOS signing and build processes, so you need to get the provisioning profile onto it first:

• Transfer the appidentifierIOS.mobileprovision file to your remote Mac (use a shared folder, email, or whatever file transfer method you normally use).
• Double-click the file—it should automatically launch Xcode (if Xcode is installed on the Mac). Xcode will install the profile to the correct system location without any extra steps.
• If Xcode doesn’t open, you can manually place it in the Mac’s provisioning profiles folder: ~/Library/MobileDevice/Provisioning Profiles/ (note: the Library folder is hidden by default; press Cmd + Shift + G in Finder and paste the path to access it).

2. Configure Visual Studio 2017 (Windows) to Use the Profile #

Once the profile is on the Mac, link it to your iOS project in VS:

• Open your iOS project in Visual Studio 2017.
• Right-click your project in the Solution Explorer and select Properties.
• Navigate to the iOS Bundle Signing tab.
• Under the Provisioning Profile dropdown, you should see your appidentifierIOS.mobileprovision listed. If it’s missing, click the Refresh Provisioning Profiles button—VS will sync all profiles from your remote Mac.
• Make sure the Signing Identity dropdown matches the one tied to your appidentifier.p12 certificate (the one you already installed on the Mac).

Critical Checks to Avoid Push Failures #

• Verify your .mobileprovision includes push permissions: Double-click the profile on the Mac to open it in Xcode, then check the Entitlements section for the aps-environment key. It should be set to development (for testing on simulators/devices) or production (for release builds).
• Ensure your appidentifier.p12 is accessible to VS: When installing the p12 file on the Mac, check the box that says Allow all applications to access this item—this lets Visual Studio’s remote connection use the certificate for signing.

内容的提问来源于stack exchange，提问作者Developer