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.
Created attachment 1987 [details]
controller file to display the pdf file using MVVMCross library
My app successfully display pdf report file on iPad/iPhone when running with monotouch version 5.2.5; after upgrading to 5.2.12 the app was frozen after the report is displayed on the device, the screen was completely frozen. Could only hit home key to go back the the home window, when I select the app icon to launch it again, it went back to the frozen pdf view.
I contacted supported, spoke with Chris to ask for help rolling back to version 5.2.5. After reinstall monotouch to version 5.2.5, this frozen view problem went away, the app is working again. We are using MVVM cross platform library to display our reports. Attached is the piece of code that was call to display the pdf file in the view
Can you create a crash report for this hang by following the instructions here: http://rolfkvinge.blogspot.com.es/2012/05/monotouch-debugging-tips.html ?
That should tell us what the app is trying to do when it hangs.
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?
If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.
Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.