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.
Created attachment 13101 [details]
Logs from my repo of the issue
Extremely slow app launch time on iPhone 4 iOS 7.1 device. This occurs both when trying to debug & when launching an already installed app independently. When trying to debug it fails with the following error:
> error MT1107: Application failed to launch: Etimed out trying to launch app
(Yes, it does say "Etimed", I'm filing a separate minor bug for that issue).
## Steps to reproduce
1. Create a new iOS Single View Unified Template App
2. Set the deployment target to 7.1 (or lower)
3. Build and deploy the app
## Expected Results
App should deploy and connect to the debugger.
## Actual results
App is installed, and in some tests seems to at least (partially) complete launching, but then stops, and Xamarin Studio gives the MT1107 error message above. After the app is installed, if you tap it on the device, iOS becomes unresponsive for several seconds, but then launches the app which seems to work as normal.
(This is why I suspect this is an "iOS" rather than a "Xamarin Studio" bug, since slow launching behavior is observed independently of any debugging / deploying steps within Xamarin Studio itself.)
## Build Information
=== Xamarin Studio ===
Version 5.9.7 (build 9)
Installation UUID: 8ef63a7c-1b18-40de-a334-7f78777fcb55
Mono 4.0.4 ((detached/cb6d6b2)
GTK+ 2.24.23 (Raleigh theme)
Package version: 400040002
=== Apple Developer Tools ===
Xcode 6.4 (7720)
=== Xamarin.iOS ===
Version: 184.108.40.206 (Business Edition)
Build date: 2015-09-18 23:22:05-0400
=== Xamarin.Android ===
Version: 220.127.116.11 (Business Edition)
Android SDK: /Users/kentgreen/Library/Developer/Xamarin/android-sdk-macosx
Supported Android versions:
4.0.3 (API level 15)
4.1 (API level 16)
4.2 (API level 17)
4.3 (API level 18)
4.4 (API level 19)
4.4.87 (API level 20)
5.0 (API level 21)
5.1 (API level 22)
Java SDK: /usr
java version "1.8.0_51"
Java(TM) SE Runtime Environment (build 1.8.0_51-b16)
Java HotSpot(TM) 64-Bit Server VM (build 25.51-b03, mixed mode)
=== Xamarin Android Player ===
Version: Unknown version
Location: /Applications/Xamarin Android Player.app
=== Xamarin.Mac ===
Version: 18.104.22.168 (Business Edition)
=== Build Information ===
Release ID: 509070009
Git revision: 31fa64709030b3edb971237780a452a4c69943c4
Build date: 2015-09-17 11:44:37-04
Xamarin addins: b105d33d8cd72911ff2cf3ee0b7715d37e5f19a6
=== Operating System ===
Mac OS X 10.10.5
Darwin Kents-MBP 14.5.0 Darwin Kernel Version 14.5.0
Wed Jul 29 02:26:53 PDT 2015
## Additional Info
The build information above was using Xcode 6.4, though I'm also seeing the same behavior on Xcode 7 & Xcode 7.1 beta. (i.e. changing Xcode versions seemed to have no impact on the bug.)
Additionally, I was able to observe that the app seemed to have no such problems running in the iPhone 4s iOS 7.1 simulator / Xcode 6.4. (This was the closest simulator approximation to my iPhone 4 iOS 7.1.1 test device.)
Adding Xamarin Studio logs.
Adding Bug 34357
> Typo in error message "error MT1107: Application failed to launch: Etimed out trying to launch app"
as a "see also" link.
Could you try a few things to narrow this down?
1) Try creating another Xamarin.iOS app, and see if that is slow as well.
2) Try creating an Xcode app, and see if that is slow as well.
3) Try rebooting the device; does anything change?
We have not received the requested information. If you are still experiencing this issue please provide all the requested information and re-open the bug report. Thanks!