The original report on your issue has been closed recently. Please note that you will not be able to directly view the original report in order to keep its information confidential. If you have further questions about this issue, please update your report using the Apple Bug Reporter http://bugreport.apple.com.
This might be caused by users pirating the app. This can cause an app to have invalid iCloud entitlements, which in turn will make UIDocumentPickerViewController throw an exception.
So not a bug in UIKit, it's doing the right thing.
It appears you can workaround this by setting a baseline offset of 0. I am working in Xamarin Studio, and the following resolved the issue for me:
var attributedString = new NSMutableAttributedString(text);
attributedString.AddAttribute(UIStringAttributeKey.BaselineOffset, NSNumber.FromInt32(0), new NSRange(0, message.Length));
attributedString.AddAttribute(UIStringAttributeKey.StrikethroughStyle, NSNumber.FromInt32((int)NSUnderlineStyle.Single), new NSRange(0, message.Length));
Hopefully this works when translated to Swift too. It looks like this bug is related to:
Did you ever find a solution to this or get an update from Apple? We are seeing similar issues. Thanks!
Did you ever find a solution to this or get an update from Apple? We are seeing similar issues.
The original report on your issue has been closed recently. Please note that you will not be able to directly view the original report in order to keep its information confidential.
If you have further questions about this issue, please update your report using the Apple Bug Reporter http://bugreport.apple.com.
The bug was (finally) fixed in macOS 10.12.4 and the workaround is no longer necessary (except for backward compatibility, of course).
Reproduction (iOS viewable) link expired. Please use the following for reproduction:
[MC] Reading from public effective user settings.
libMobileGestalt MobileGestaltSupport.m:153: pid 4409 (PinPoint Xtra) does not have sandbox access for frZQaeyWLUvLjeuEK43hmg and IS NOT appropriately entitled
libMobileGestalt MobileGestalt.c:550: no access to InverseDeviceID (see )
This very poor error message is caused by a type error: xmlData(withOptions:) expects an Int, but XMLNode.Options.nodePrettyPrint.rawValue is a UInt. A better workaround is using the one used in the XMLDocument constructor: cast the rawValue to the right type, like document.xmlData(withOptions: Int(XMLNode.Options.nodePrettyPrint.rawValue)).
This issue behaves as intended.
We are now closing this bug report.
If you have questions about the resolution, or if this is still a critical issue for you, then please update your bug report with that information.
Please be sure to regularly check new Apple releases for any updates that might affect this issue.
See here: http://stackoverflow.com/a/43478888/3195266
Engineering has determined that your bug report is a duplicate of another issue and will be closed.
The open or closed status of the original bug report your issue was duplicated to appears in the yellow "Duplicate of XXXXXXXX" section of the bug reporter user interface. This section appears near the top of the right column's bug detail view just under the bug number, title, state, product and rank.
If you have any questions or concerns, please update your report directly here: http://bugreport.apple.com/.
I don't remember what values I entered for Classification and Reproducibility on this bug, but I meant to enter "Crash/Hang/Data Loss" and "Always". Oh, the irony.
Engineering has provided the following feedback regarding this issue:
Thank you for your feedback.
Marked as Duplicate of 26939947 (Open).
Issue is still present in iOS 10.3.1