Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode. Please join us on and in the and organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links. Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.
Please create a new report on with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report. Guillaume 2015-10-15 09:31:16 UTC%% Steps to reproduce 1.
Create a unified iPhone HelloWorld project (Blank) 2. In project options: - Enable IPA generation for configs Realease/iPhone & AppStore/iPhone - Assign a proper application identifier in order to allow build configurations to succeed (development and distribution certificate) 3. Close Visual Studio and open a Visual Studio Developer Command Prompt 4. Run the command `C: Path To The Solution TheTestSolution.sln /p:Configuration=Release;Platform=iPhone`%% Expected results The build should be properly performed locally && remotely on the mac in order to allow the IPA generation (for both Release and AppStore configurations).%% Current results Only the local build is performed.%% Details This was properly working with Xamarin for Visual Studio 3.11 (we have been using it in our TFS builds since December 2014) but seems no longer functional since 4.0. Find attached the build log from the Windows box.
I think the important part is about the _SayHello target which was already used in Xamarin.VS 3.11 but no longer properly runs since 4.0. `(_SayHello target) -> C: Program Files (x86) MSBuild Xamarin iOS Xamarin.iOS.Windows.After.targets(54,5): warning VSXRunBuildLocally: The project TestRemoteBuild was built while disconnected from a Mac agent, so only the main assembly was compiled. Connect to a Xamarin Mac build agent to build the full application. [C: Users ggirard Documents Visual Studio 2013 Projects TestRemoteBuild TestRemoteBuild TestRemoteBuild.csproj]`%% Versions > Windows box Microsoft Visual Studio Premium 2013 Version 12.0.40629.00 Update 5 Xamarin 4.0.0.1566 (5abb0de) > OS X Box OS X Yosemite 10.10.5 Xamarin.iOS Version: 9.2.0.84 (Business Edition) Hash: b5396c2 Branch: master Build date: 2015-09-30 15. Arpit Jha 2015-10-16 05:19:48 UTC I have checked this issue and able to reproduce this issue with the help of bug description build using Xamarin.VisualStudio_4.0.0.157abbb98b1b6e751ed8428dff3d6fee28d monotouch-9.2.0.93_1a6b88f2b2305d50bad065ae4c7292ab6348ff60 Build output: REGRESSION: This issue is working fine with latest stable build Xamarin.VisualStudio_3.11.1537_a11147b697db127e63af3b0811811a01c30a178e monotouch-9.0.1.29_1d27ac2cea28ce4baac7ca238122e0a8aea5d17a Build output: Environment Info: Windows: Mac.
How To Create Ipa File Using Provision File
Hi @AnBucyk, I have Visual Studio 2017 and used Cordova 7.0 and ios 8.3.1 and Mac 10.X. I am able to successfully build the solution and getting the ipa and plist. I am able to successfully build the solution and getting the ipa and plist. I'm developing my project in Visual Studio 2012 using Xamarin Monotouch. I choose profile Ad-Hoc, specify signing information (provision profile, identity etc) and build my project. But I see no IPA file generated neither on my PC, nor on Mac. I tried to find it, but it was unsuccessful. It happens even in new HelloWorld project. Did you know you can report issues with Visual Studio 2017 or Visual Studio for Mac directly within the IDE? Just use Help > Report a Problem to file your issue. I was unable to get the app deployed to the App store because it would not detect the icons in the IPA file. 
To workround this issue, I recreated the project on Visual Studio for Mac after which I could deploy to the App Store without an issue.