Bug 23093 - v8.0.52.0: "Show IPA" in VS command broken, because IPA generated in wrong folder
Summary: v8.0.52.0: "Show IPA" in VS command broken, because IPA generated in wrong fo...
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS ()
Version: 3.6
Hardware: PC Windows
: Normal normal
Target Milestone: 3.7
Assignee: Bugzilla
Depends on:
Reported: 2014-09-17 08:13 UTC by softlion
Modified: 2014-09-30 07:37 UTC (History)
6 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono 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 Developer Community 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.

Related Links:

Description softlion 2014-09-17 08:13:22 UTC
After compiling an ios app from visual studio with the adhoc profile, the "show ipa" command fails.

I've checked and the IPA file is correctly generated, but in the "obj" folder.
Comment 1 Sebastien Pouliot 2014-09-17 09:38:28 UTC
@jeff was not that already solved (in the msbuild tasks iirc) ? 
Maybe it's not yet released ?
Comment 2 Jeffrey Stedfast 2014-09-17 09:47:55 UTC
yea, it was fixed last week. I think the VS guys just need to update their MSBuild targets.
Comment 3 Mohit Kheterpal 2014-09-30 07:37:14 UTC
I have checked this issue and now "Show IPA file in finder" is working fine with XVS 3.7.178 + X.iOS

Hence closing this issue.