iOS Workaround for MSConversation's insertAttchment:withAlternateFilename: ???

[Cosmosent]

It's a known bug (rdar://28278392).

Just wondering if anyone has a viable work-around they would like to share.

The Bug was first filed on Sept 13, 2016 ... I can confirm the Bug still exists today, @ iOS 12.3.1

 

[PhoneyDeveloper]

I don't know anything about that API but you have a couple options. If you filed that radar you can send devbugs an email request to ask the status of the bug and if there is a workaround. If you didn't file it then go ahead and file one and then ask for the update. If that doesn't help you can use one of your 2 code level support requests to ask for help from Apple. If they can't help you they don't charge you the incident. The code level support request gives you direct access to someone at Apple that should be able to either help you or tell you there's no workaround.