After updating to Visual Studio 2019 Ver16.9.2, the Xamarin forms iOS Release Build failed to find the provisioning file.

Asked 2 years ago, Updated 2 years ago, 114 views

At Visual Studio 2019, we are developing iOS and Android apps using xamarin forms (for the first time with Xamarin forms).
I was able to register the release version in the App Store the other day, but when I upgraded the version (Ver16.9.2), the following error occurred in the iOS Release Build and the ipa file was no longer created.

The specified iOS provisioning profile 'xxx' could not be found. Please enable Automatic Provisioning from the iOS Bundle Signing page.

You have selected a valid signature ID and a valid provisioning profile.
I would appreciate it if you could tell me how to avoid it.

Tried

  • Re-creating and executing the provisioning file has the same result (expanded to combo box and selected).
  • Tools-Options-Xamarin-Apple Accounts displays the certificate as valid in the detailed view, and the provisioning profile expires sufficiently.

--- <>-----
● The questions I asked you (no provisioning profile found) have been resolved by doing the following:
Visual Studio 2019 Tools Options Xamarin Apple Accounts ·Download all profiles from the details view (this behavior has never been done before).
The does not create an IPA file and creates an exe file.The iOS IPA option is Build IPA.
● Also, if you view the IPA file on the tool iOS build server, it will be displayed on the last release date on the paired Mac, but at the same time exe was present and the date was the same (Windows bin contains almost the same file, but exe is the current date and time).
● Does this mean that before (before VS upgrade) the IPA file was created by building on the Mac, and now the IPA file is not created by building on Windows?
My wish is to create an IPA file.Could you please let me know if anyone knows?Thank you for your cooperation.

ios c# visual-studio xamarin

2022-09-29 22:30

1 Answers

Why don't you update your Xcode to the latest version?
It's not the same as the questioner's case, but
I have been able to build but now I have failed to build.
In my case, I ended up building with iOS update, Xcode update, VS2019 for Mac update (forgotten order).
Be careful and take your own responsibility.


2022-09-29 22:30

If you have any answers or tips


© 2024 OneMinuteCode. All rights reserved.