Bug 4185 - New builds should not be required to create appstore/adhoc .IPAs
Summary: New builds should not be required to create appstore/adhoc .IPAs
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: iOS add-in ()
Version: Trunk
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Jeffrey Stedfast
URL:
Depends on:
Blocks:
 
Reported: 2012-04-02 09:34 UTC by Jackson Harper
Modified: 2013-03-08 19:29 UTC (History)
2 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 Jackson Harper 2012-04-02 09:34:46 UTC
I think the process for signing applications is a little flawed. In XCode, you create a build (an application archive) and then you sign that build for adhoc or appstore deployment.

MonoDevelop/MonoTouch requires you create a new build each time you sign your application. So the build that you submit to the appstore is not the same one that you test. 

This becomes a problem if anything goes wrong with the build, we build against multiple branches and sometimes resource files don't get copied over properly.  But the real problem is you can't have confidence in the build you submitted is identical to the one you tested.
Comment 1 Jackson Harper 2012-04-02 09:41:27 UTC
Sorry, I should add:  Yes, I know I can re-sign the application myself and avoid the file copying issues by clearing out build directories.
Comment 2 Jeffrey Stedfast 2012-04-05 18:51:19 UTC
You bring up some interesting points... perhaps MonoDevelop needs a Publish command that will allow you to publish an existing Release build for Ad-Hoc or AppStore distribution.

Miguel just asked me to create Ad-Hoc|iPhone and AppStore|iPhone build configurations for MonoTouch projects by default, but perhaps that is not the best approach.
Comment 3 Jeffrey Stedfast 2012-09-20 12:05:28 UTC
I recently added a feature to MonoDevelop to archive the latest build in the current build configuration. I think it may have made it into 3.0.4 (would need to double-check to confirm).

At that point, you'd use Xcode's Archive Organizer UI to publish.

This probably doesn't provide the full features you're looking for, but I think it's probably a step in the right direction.

Does Xcode's Archive Organizer allow you to resign? How do you publish as Ad-Hoc?

I've only seen that it will let me publish to the App Store and didn't seen an option to resign.

Just trying to figure out what parts I'll need to implement in MonoDevelop to finish up this feature request.
Comment 4 Jeffrey Stedfast 2013-03-08 19:29:12 UTC
To answer some of my own questions:

Yes, Xcode's Archive Organizer *forces* you to resign when you click the "Distribute..." button.

The "Distribute..." button gives you a multiple-choice screen to let you choose how to distribute, one of the choices being Ad-Hoc (the others being Enterprise, App Store and I think "copy the archive to specified location")


That said, I've implemented the "Validate..." and "Distribute..." buttons in MonoDevelop's Archive window, so this should no longer be an issue.