Bug 14878 - SpringBoard: the app could not start (error -3)
Summary: SpringBoard: the app could not start (error -3)
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Debugger ()
Version: 1.4.x
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Dominique Louis
Depends on:
Reported: 2013-09-20 09:46 UTC by Allie Miller
Modified: 2016-05-10 17:02 UTC (History)
10 users (show)

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

Test Case from Case #46672 (26.87 KB, application/zip)
2013-09-20 09:46 UTC, Allie Miller
Trace Log from Case #46672 (11.83 KB, application/octet-stream)
2013-09-20 09:47 UTC, Allie Miller
Mac Server Log from Case #46672 (8.74 KB, text/plain)
2013-09-20 09:48 UTC, Allie Miller
mtbserver log from Case #46672 (23.11 KB, application/octet-stream)
2013-09-20 09:48 UTC, Allie Miller

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 Allie Miller 2013-09-20 09:46:25 UTC
Created attachment 4936 [details]
Test Case from Case #46672

When deploying the attached sample application to the iOS 6, 6.1 or 7.0 simulator via Visual Studio, the error message appears. However, when attempting to the iOS 5 simulator via Visual Studio, the deployment is successful. 

Deployment to the iOS Simulators via Xamarin Studio is successful. 

Mtbserver log, trace log and Mac Server output attached.

Versioning information:

=== Xamarin Studio ===

Version 4.0.12 (build 3)

Installation UUID: 47b19ecc-96fb-4d4c-a45d-5decb317cfa0


Mono 3.2.3 ((no/8d3b4b7)

GTK 2.24.20

GTK# (

Package version: 302030000

=== Apple Developer Tools ===

Xcode 5.0 (3332.25)

Build 5A1413

=== Xamarin.iOS ===

Version: (Business Edition)

Hash: aa35ba3


Build date: 2013-18-09 16:42:48-0400

=== Xamarin.Mac ===

Xamarin.Mac: Not Installed

=== Xamarin.Android ===

Not Installed

=== Build Information ===

Release ID: 400120003

Git revision: 593d7acb1cb78ceeeb482d5133cf1fe514467e39

Build date: 2013-08-07 20:30:53+0000

Xamarin addins: 25a0858b281923e666b09259ad4746b774e0a873

=== Operating System ===

Mac OS X 10.8.5

Darwin macbook.afg.ads 12.5.0 Darwin Kernel Version 12.5.0

Mon Jul 29 16:33:49 PDT 2013

root:xnu-2050.48.11~1/RELEASE_X86_64 x86_64
Comment 1 Allie Miller 2013-09-20 09:47:34 UTC
Created attachment 4937 [details]
Trace Log from Case #46672
Comment 2 Allie Miller 2013-09-20 09:48:14 UTC
Created attachment 4938 [details]
Mac Server Log from Case #46672
Comment 3 Allie Miller 2013-09-20 09:48:55 UTC
Created attachment 4939 [details]
mtbserver log from Case #46672
Comment 4 Brendan Zagaeski (Xamarin Team, assistant) 2013-09-20 15:03:31 UTC
This looks similar to an issue under seen under OS X on a forum post, so this might not be VS-specific:
Comment 5 Alan McGovern 2013-10-31 14:33:32 UTC
Fixed in https://github.com/xamarin/XamarinVS/commit/b75ed330a5976c065abee078b0eeb45314c268dd

The workaround is to open your project settings, open the iOS Application section, then fill in a value for Application Name and Identifier.

Application name can be any plain text string.
Identifier is any string in the form:  com.foo.bar

I don't know how strict iOS is on these strings, but the above should always work ok.
Comment 6 kerschl.alexander 2013-11-04 02:26:18 UTC
The workaround does not work for me, because even I press the save button, the fields Application Name, Identifier and Version are not saved. i.e. if I close the window and open it again the Input fields are empty....
Comment 7 kerschl.alexander 2013-11-04 05:19:44 UTC
additional information:

the settings are saved, when I edit the "Info.plist" file directly!

It does not work, when editing via the APP - Properties...
Comment 8 Alan McGovern 2013-11-04 10:18:55 UTC
This issue was fixed recently, could you try the latest Xamarin.iOS for VS alpha? Version 1.8 should be available in the Alpha channel and should contain a fix for the bug where you can't save all the changes in the info.plist file.

One other thing, when the iOS simulator has been launched you may have to use 'Reset Content and Settings' option in the iOS simulator itself. That should wipe any broken files/settings from the simulator if they aren't automatically wiped/replaced when you upload the fixed Info.plist.

I'll close the bug again once you confirm everything is working as expected.
Comment 9 kerschl.alexander 2013-11-04 10:28:06 UTC
Thanks- the workaroud works for me....