Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
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.
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.
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.
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.
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.