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 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.
Can you please provide the device logs also?
@Rodrigo, Here is the device log: https://gist.github.com/Asimk360/82d19c7d5d3d781524b7452b3b8a3bab
The profiler does not work on IOS.
Create new project
Select Debug > iPhoneSimulator
Run > Start Profiling
Profiler application starts
Start Button Greyed out.
Sometimes i get this dialog at startup
could not open /var/folders/94/qfz_5g0j73q8dd5st_y6m1lm0000gq/T/tmp5d532025.tmp
This has been this way for months..
Profiler is totally useless since it cant be started..
@Asim, from that log, it is starting the debugger, not the profiler:
In the IDE/Profiler logs all look ok, it's just waiting for the data to come, which never happens, so it looks like it can't reach indeed the iOS device.
What about simulators? it works there, right?
@Mitchell please attach the profiler/device logs, and we'll have a look.
@Rodrigo, Profiling is working fine with simulator, here is the screencast:
Screencast with Simulator: http://www.screencast.com/t/gpmjEOLc
Screencast with Device: http://www.screencast.com/t/LlmCoZ5Ac
Fixed in version 0.33.2.2 (master)
Author: Rodrigo Moya
Commit: d46238924c95edc8633dd05944f394dcfa6f05b0 (xamarin/profiler)
After watching the screen cast we realized that even with the latest Xamarin Studio, the profiler was still a very old version. Had to delete profiler from machine and download it again, and double check that version 0.33.2 was specified..
Not sure if the fact that profiler did not update is a bug, but we at least can see the expected functions for the profiler.
This issue does not exist with latest profiler build i.e. 0.33.2.79. Here is the screencast for the same: http://www.screencast.com/t/Db3rvlTRU0Js