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.
It changed in Xamarin.iOS 6.2.6. But such UIKit function usually thread safe and these aren't exceptions.
So, why ensuring UI thread?
We had a discussion with Apple engineers about the selectors/functions we marked as [ThreadSafe]. It turns out a few of them were wrong, i.e. not thread-safe. AsJPEG being one of them.
Sad. Do you know any case when AsJPEG or AsPNG will show it's "thread-not-safety"? Just curious.
Thanks for response anyway.
After re-reading the emails I found out the answer was filtered, i.e. some items* were removed to show us only the non-thread safe methods/selectors.
* exactly those two UIImagePNGRepresentation and UIImageJPEGRepresentation - but I'll re-read the whole email thread again to be 100% sure we did not make another mistake.
Thanks a lot for reporting and asking details :-)
fixed in 9994a9dee8b65f0631cd260627e0d7fbb5a93d0c
As Sebastien discovered, I misread the email, and those methods are thread safe.
A fix is now available on the stable channel.