Bug 5641 - MonoDevelop Debug & Release mode uploads to iOS device create separate applications
Summary: MonoDevelop Debug & Release mode uploads to iOS device create separa...
Alias: None
Product: iOS
Classification: Xamarin
Component: Tools ()
Version: 5.3.x
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: 7.0.6
Assignee: Bugzilla
Depends on:
Reported: 2012-06-13 19:27 UTC by Joseph Hanna
Modified: 2013-12-17 08:54 UTC (History)
5 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 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:

Description Joseph Hanna 2012-06-13 19:27:33 UTC
When deploying to an iOS device, if you are in Debug mode it will correctly install the application.  If you then switch to Release mode and deploy it to the device, you end up with a second instance of the application on the home screen an associated folders - as though it was a completely separate application.

Installation UUID: 075386b0-58e8-4bee-92bd-faf016b46d99
	Mono 2.10.9 (tarball)
	GTK 2.24.10
	GTK# (
	Package version: 210090011
Mono for Android not installed
Apple Developer Tools:
	 Xcode 4.3.2 (1177)
	 Build 4E2002
Monotouch: 5.3.4
Build information:
	Release ID: 30003001
	Git revision: 1b6ffb8235519a006d51afd98014ad20186cfd1b-dirty
	Build date: 2012-06-08 08:39:08+0000
	Xamarin addins: 62ad7268d38c2ece7e00dc32960bd3bdab8fec38
Operating System:
	Mac OS X 10.7.4
	Darwin Josephs-MacBook-Pro.local 11.4.0 Darwin Kernel Version 11.4.0
	    Mon Apr  9 19:32:15 PDT 2012
	    root:xnu-1699.26.8~1/RELEASE_X86_64 x86_64
Comment 1 Sebastien Pouliot 2012-06-19 21:52:23 UTC
This could be due to different options being specified in the Debug and Release configuration. E.g. having different values for the identifier in Project's options, iPhone Application.

Could you attach the .csproj of your main application to the bug report ?
Comment 3 Joseph Hanna 2012-06-19 22:01:17 UTC
The identifier in the project is blank.  I didn't release you could have one for Debug and one for Release.

I only noticed this behaviour once I installed
Comment 4 Joseph Hanna 2012-06-19 22:01:48 UTC
Comment 5 Rolf Bjarne Kvinge [MSFT] 2012-06-20 07:44:55 UTC
Does it work as expected if you use the same identifier for both Debug and Release targets?
Comment 6 Joseph Hanna 2012-06-20 07:49:25 UTC
How do you specify a different Identifier under "iOS Application Target"?

When I populate this field with Debug set, it is still there when i change the target to "Release".
Comment 7 Rolf Bjarne Kvinge [MSFT] 2012-06-20 07:54:51 UTC
The "iOS Application" Target field is project-wide, so you'll only need to set it once. Does it work if you set this field to something?
Comment 8 Joseph Hanna 2012-06-20 09:30:22 UTC
No.  I just got this one now (tried to connect to my iPhone):

/Developer/MonoTouch/usr/bin/mtouch -sdkroot "/Applications/Xcode.app/Contents/Developer" -installdev "/Users/joe/Projects/Mono/ACR/SalesTALK/SalesTALK/SalesTALK/bin/iPhone/Debug/ACRSalesTALK.app"
Please ensure your device is connected...
Connected to: Joseph’s iPhone 4S
Initializing file service...
Installation failed: AMDeviceStartService returned: 0x0 (kAMDSuccess)
error MT1006: Could not install the application '/Users/joe/Projects/Mono/ACR/SalesTALK/SalesTALK/SalesTALK/bin/iPhone/Debug/ACRSalesTALK.app' on the device '': AMDeviceStartService returned: 0x0 (kAMDSuccess).
The application was terminated by a signal: SIGHUP


If I unplug iPad3 and plug it back in, it uploads straight away ("Run" => "Upload to Device").  If I try to do it again straight away, I get this:-

/Developer/MonoTouch/usr/bin/mtouch -sdkroot "/Applications/Xcode.app/Contents/Developer" -installdev "/Users/joe/Projects/Mono/ACR/SalesTALK/SalesTALK/SalesTALK/bin/iPhone/Debug/ACRSalesTALK.app"
Please ensure your device is connected...
Connected to: Joseph’s iPad 3
Initializing file service...
Uploading application
Finalizing file service...
Installation failed: AMDeviceTransferApplication returned: 0x0 (kAMDSuccess)
error MT1006: Could not install the application '/Users/joe/Projects/Mono/ACR/SalesTALK/SalesTALK/SalesTALK/bin/iPhone/Debug/ACRSalesTALK.app' on the device '': AMDeviceTransferApplication returned: 0x0 (kAMDSuccess).
The application was terminated by a signal: SIGHUP


If I unplug it and plug it straight back in, it works fine. Looks like I only get one go before having to unplug it and plug it back in again.
Comment 9 Sebastien Pouliot 2012-06-20 09:43:02 UTC
That's likely a different issue so I filled #5776 with the above. You can add yourself to the c.c. list
Comment 10 Sebastien Pouliot 2012-06-20 09:46:34 UTC
Joseph, I could not see anything wrong in your csproj (like any custom task that could affect the name).

Can you, for both Release and Debug, do the following:
* add "-v -v" to your project options;
* Clean and rebuild your application
* attach the "Build Output" (from the Error List pad)
Comment 11 Joseph Hanna 2012-06-20 18:31:00 UTC
Hi Sebastien,

Where exactly should I be adding "-v -v"?

Comment 12 Sebastien Pouliot 2012-06-20 21:17:03 UTC
Inside MonoDevelop, right click on your main project (exe) and select Options, iPhone Build, then add "-v -v" to the "Additional mtouch arguments"
Comment 13 PJ 2013-11-19 17:04:07 UTC
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?

If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
Comment 14 Joseph Hanna 2013-11-19 17:08:27 UTC
I have seen this happen again.  It was on an old version of MonoDevelop.

I am happy for you to close this.
Comment 15 Joseph Hanna 2013-11-19 17:12:14 UTC
*haven't seen*
Comment 16 Sebastien Pouliot 2013-11-19 17:35:27 UTC
Thanks for confirming!
Comment 17 PJ 2013-12-11 18:45:49 UTC
This fix is planned to be released with Xamarin.iOS 7.0.6, which should hit the beta channel before December 23rd.
Comment 18 Mohit Kheterpal 2013-12-17 08:54:10 UTC
As per comment 14 and comment 15, this issue does not exist any more.

Hence closing this issue.