6

I'm trying to open a mail composer via UIActivityViewController on iOS8. (So, there's no my own code for this procedure) The result on device is continues error logging (the messages continue to be logged even after I close mail and quit to different UI controller)

AX Exchange error: Error Domain=Accessibility Code=0 "Remote service does not respond to _accessibilityMachPort" UserInfo=0x14fd1b60 {NSLocalizedDescription=Remote service does not respond to _accessibilityMachPort}

On a simulator the MFMailComposeViewController just dismisses right after I present it with error:

viewServiceDidTerminateWithError: Error Domain=_UIViewServiceInterfaceErrorDomain Code=3 "The operation couldn’t be completed. (_UIViewServiceInterfaceErrorDomain error 3.)" UserInfo=0x7b6eb4b0 {Message=Service Connection Interrupted}

P.S. I have xcode 6 and testing on iOS 8.0.2 iPhone 5s. Am I doing something wrong? Thanks in advance for your replies!

narner
  • 2,908
  • 3
  • 26
  • 63
Stas
  • 9,925
  • 9
  • 42
  • 77
  • Have you been able to explain or resolve this? – Drux Feb 13 '15 at 21:34
  • unfortunately not :( – Stas Feb 17 '15 at 13:49
  • I see. I'm seeing these messages as well: see [here](http://stackoverflow.com/questions/28515414/kif-output-ax-exchange-error-error-domain-accessibility-code-0-remote-service) – Drux Feb 17 '15 at 16:06
  • let me know if you fix this plz – Stas Feb 18 '15 at 12:02
  • I've found out a bit more (see [here](http://stackoverflow.com/a/28592706/1789384)). – Drux Feb 18 '15 at 19:56
  • Same problem, so far I've only tested on the simulator - with the exact same failure and message. (My test case is pretty minimal, not sure how we could be causing this problem.) Anyone try to file a bug with Apple? – jbbenni Mar 15 '15 at 21:56
  • Same exact thing happens using MPMediaPickerController. – phatmann Jun 11 '15 at 12:07

1 Answers1

0

I came across same problem in my product and after doing some debugging, I narrowed down that it's the combination of presented ViewController and custom keyboard. That means my application was showing this error message only when I navigated to any presented ViewController (like mail composer) and a custom keyboard was activated.

During further hit-and-try, I was able to get rid of this error message by removing MonkeyTalk library, which was being used for automated testing.

I am not sure if same scenario applies to you, but I am sure that some library is conflicting with some keyboard and that's resulting in error message.

P.S. in my case my application was being freezed by those error messages.

Dipak Mishra
  • 187
  • 12
  • I got same problem as Stas and exact same message, without using a custom keyboard and without the MonkeyTalk Library. – jbbenni Mar 15 '15 at 21:57
  • @jbbenni I am not sure if this applies to your case or not, but there must be some 3rd party library, that is conflicting with keyboard. Try removing any 3rd party library and see if it solves your problem. – Dipak Mishra Mar 23 '15 at 05:50
  • The only libraries I link are: CoreText, MessageUI, UIKit, Foundation, and CoreGraphics. I'd be surprised if those were incompatible or conflicted with Apple mail controller. Not sure why you think it's a keyboard conflict. My symptoms are identical to Stas (above). – jbbenni Mar 24 '15 at 15:45
  • Correction: I get EXACTLY the same symptom on the simulator, but the mail function appears to work properly on an actual iPad device. Perhaps there are two problems: 1) Apple broke email on the simulator, and 2) some other issue is muddying the water. See this question: http://stackoverflow.com/q/25801366/1035697 – jbbenni Mar 24 '15 at 22:30