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.
Scenario: After compiling and deploying to an iOS device, if the MonoTouch application is removed from the iOS device, the next time a user clicks 'Run' or 'Debug' in MonoDevelop the application is NOT launched and the message 'Could not find application 'AppName' on device 'DeviceName' is shown in the Application Output.
If the application is not on the device MonoTouch should redeploy it.
1. Build / Deploy a MonoTouch app to an iOS Device
2. Remove the application from the iOS device
3. Click 'Run' or 'Debug' to re-launch the application on the Device.
Uploading can be quite slow, so this would hurt the experience for most users. We can't do this unless mtouch can detect and report whether the app is on the device.
mtouch can now check if an app is installed.
mtouch --isappinstalled bundleId
returns 0 if installed, 1 if not.
Probing if the app is installed is also slow.
On my machine, on first run it takes about 5 seconds to start.
On warm setups, it takes 1.29 seconds.
What I suggest is that we make it so that we proceed with the execution path as we have it now, and if we fail, only then we probe for the app being there, if it is, we report the problem to the user. Otherwise, we upload, and retry the process.
At least in this way, not everyone has to pay the 1.2 seconds to probe on cold/ warm starts,
implemented in git master