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.
In windows, we are not able to open the MLPD files generated in iOS. This happens after the Xamarin profiler upgraded to 0.23.0.0 version. Even same with the latest 0.24.0.0 version.
Xamarin Studio 5.9.1 (build 3)
Xamarin Profiler 0.24.0.0
Visual Studio 2015
Steps to Reproduce:
1. Make sure the device is connected with the Mac and Xamarin studio detected the device.
2. Launch the Xamarin profiler from Xamarin studio.
3. Run the Xamarin profiler and get the result for any scenario.
4. Save the result as MLPD file in IOS machine
5. Transfer the MLPD file to windows machine
6. Open the MLPD file with Xamarin profiler in windows
Xamarin Profiler gets hanged and will throw error message “XamarinProfiler.Windows has stopped working”
In windows, should be able to open MLPD generated in iOS.
In windows, using Xamarin Profiler version 0.19.0.0, we were able to open the MLPD files generated in iOS.
Can you confirm when using the latest version of the Profiler to create the actual mlpd, it id still getting corrupted.
Local testing suggests it works.
So to confirm you generated the mlpd file on Mac, then opened it on Windows?
We are not getting any response for this issue. So as of now, I am changing it's status to "NORESPONSE".
Please feel free to reopen this issue if you get it again with latest profiler build.