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.
Created attachment 23779 [details]
Bug Description:-Unable to profile the application from Visual Studio as Xamarin Profiler option is unavailable in Analyze
- Operating System Windows 10 Pro
- Microsoft Visual Studio Enterprise 2015
- Microsoft .NET Framework Version 4.7.02053
- Xamarin.VisualStudio Version- 126.96.36.1993 (53465e0)
- Xamarin. Android Version - 188.8.131.52 (bbf378a)
- Xamarin.iOS - 10.14.0.0 (38d3a2b)
- XamarinProfiler.Windows Version -1.5.6-27
- Xamarin.Simulator.Version -184.108.40.206
Detailed Environment Info:- https://gist.github.com/gangrade-swati/a5d55bd27563c5936c994abd635dfe5e
1. Launch Visual Studio 2015
2. Create File -> New -> Project -> Android -> Single-View App (Android)
3. Clean and Build the project
4. Click Analyze from top menu bar
Actual Result- Xamarin Profiler option is not present
Expected Result- Xamarin Profiler option should be present in Analyze menu and user should be able to profile the application
Frequency of Reproduction:
Happens every time (100% failure rate)
Test Rail Info:
Test Suit link:- https://testrail.xamarin.com/index.php?/plans/view/50881
Build Taken from:
IDE Logs are attached.
We Checked 4 machine on 3 machine option is not displayed and on 1 machine it is working fine.Following is the build info of machine on which it is working fine
Build Info : https://gist.github.com/gangrade-swati/824b43b98a0e23373ab5b59880b43a3b
Can you please check if this can be reproducible on latest 15.4 bits?
We fixed an issue on the Activation assembly which seems to be causing this bug as well.
I am not able to reproduce this with XVS 220.127.116.112 (46cf47c3f) and Profiler 18.104.22.168 (4fceca54e).
env info: https://gist.github.com/BenBeckley/c34f144865d6d1241f0c1bcf30f84066