Bug 35 - Build and Archive option.
Summary: Build and Archive option.
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: iOS add-in ()
Version: Trunk
Hardware: Macintosh Mac OS
: Low enhancement
Target Milestone: ---
Assignee: Jeffrey Stedfast
URL:
Depends on:
Blocks:
 
Reported: 2011-07-21 13:55 UTC by James Clancey
Modified: 2012-07-16 16:34 UTC (History)
4 users (show)

Tags:
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 or GitHub 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:
Status:
RESOLVED FIXED

Description James Clancey 2011-07-21 13:55:05 UTC
It would be great if there was a build and archive option for monotouch.  If the archives are copied to the same location as xcode we will then have built in symblication for crash logs. As well as a built in way to keep track of published versions
Comment 1 Alan McGovern 2011-09-28 04:05:39 UTC
Would I be correct in saying the only difference between the normal 'Build' option we have now and the 'Build and Archive' option you describe is that the latter will copy the compiled .app package to a particular location?
Comment 2 Mikayla Hutchinson [MSFT] 2011-09-28 05:41:54 UTC
It's not quite that simple. It's copied into an "xcarchive" bundle in ~/Library/Develop/Xcode/Archives/{date}, which contains the app bundle, the DSYM debugging symbols, and some kind of info.plist manifest for the archive. Then, Xcode has a UI for managing archives. I'm not convinced that copying our apps into xcode's archive dir is the best solution, maybe we need to figure out a more general one of our own.
Comment 3 Miguel de Icaza [MSFT] 2011-10-24 12:41:48 UTC
James,

Could you outline for us what are the uses for the Build and Archive option?
Comment 4 Mikayla Hutchinson [MSFT] 2011-11-29 18:58:41 UTC
If we do this, I would like to figure out exactly the value it provides and figure out whether we can do it better, instead of delegating to Xcode.

I'm concerned that if we simply add a "Build and Archive" option that hands off to Xcode, then it will be very mysterious - the builds will effectively just disappear into a black hole. If we had our own UI for managing archived builds, we could open it up immediately after performing a build. Also, users would be able to view and delete archived builds without opening Xcode, and we could even support the same thing for Android.
Comment 5 Rolf Bjarne Kvinge [MSFT] 2012-04-18 08:28:08 UTC
I think we can just archive like this:

mkdir ~/Library/Developer/MonoDevelop/Archives/{date}/{app bundle}{time stamp}/
cp -R bin/iPhone/Release/project.app <archive dir>
cp -R bin/iPhone/Release/project.app.dSYM <archive dir>

Symbolication should just work, as long as spotlight is running and searching $HOME (which it does by default).

The main benefit I see is that the user doesn't have to manually copy the .app and .dSYM somewhere else to be able to symbolicate crash reports for published builds.

However there might be other benefits to creating an xcarchive instead of what I'm proposing (are there Apple tools that accept xcarchives as input?)

Personally I'd also like a way to view crash reports in MD (but that's a different issue of course).
Comment 6 Miguel de Icaza [MSFT] 2012-04-18 13:30:01 UTC
I like Rolf's plan.

We can build our own UI in the future if we want to.
Comment 7 Miguel de Icaza [MSFT] 2012-04-26 11:52:48 UTC
After discussing with Michael, I think we should:

* Generate an .xcarchive
* Upon completion, we open a dialog that shows the existing archives in the directory
* Create a new DocumentView that is populated with the contents of the archived directory, currently just a raw dump of all the builds, plus a button [Reveal in Finder]

This could be added to the new publish UI when we are done.
Comment 8 Jeffrey Stedfast 2012-04-26 16:37:27 UTC
is this low priority or high? I get the feeling this was meant to be high (as in, we want it for the 3.0 release), but it's marked as low.
Comment 9 Mikayla Hutchinson [MSFT] 2012-05-01 16:27:26 UTC
Clarification: we don't open a dialog, we open the archive list view.

Presumably the archive list view could also have simple a filter/sort feature, and a delete button for removing old archives.

Regarding integration with the publish command, there are really two ways to do this
(a) the publish command could create an archive automatically (or have an option for this)
(b) the archive list could have a command to publish an archive, like Xcode
Comment 10 Jeffrey Stedfast 2012-07-16 16:34:21 UTC
implemented in git master