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.
Steps to reproduce:
1. Open any application on MD
2. Debug/Run the application on any device with iOS less than 6.0.
3. Observe that it gives a pop-up "Developer Tools Access needs to take control of another process for debugging to continue. Type your password to allow this."
And when enter the password, it gives the error in the application output.
Actual result: When try to debug any application on any device, it gives a pop-up "Developer Tools Access needs to take control of another process for debugging to continue. Type your password to allow this."
And when enter the password, it gives the error in the application output. And the application gets deployed to device successfully, but does not launch automatically and the pop-up "Waiting for debugger to connect… " remains in MD forever.
And when click on the App icon on the device, the pop-up "Waiting for debugger to connect…" disappears.
Expected result: When Debug/Run any application on any device, it should deploy the application on the device and the application should get launch automatically.
Mac Mountain Lion (10.8)
MD 22.214.171.124 RC3
MT 5.3.5 RC3
Mono Framework 2.10.9_11 MDK
Note: This is working fine with the device with iOS 6.0.
Please, what is the exact message of the application output?
It looks like the net broken functionality is the app starting itself on device.
Once app is started manually, the debugger connects as normal, right? Can we test this with adding a breakpoint to make sure?
Here is the application output: https://gist.github.com/3076554
However, when we start the application manually, the debugger get connected, as the breakpoint hits but after few seconds the application crashes and the debugger gets disconnected.
Here is the device log: https://gist.github.com/3076678
This has been fixed (4413d0887e27da6f9f2c66d15cb4f4e220b805ef).
Today we have checked this issue on following builds :
XS 4.0.7(build 3)
Now we can able to deploy and launch the application on device with iOS < 6 successfully on Mountain lion.
Hence closing this issue. Changing its status to verified fixed.