Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AX Exchange error when MFMailComposeViewController has been initialized. #108

Closed
PikaRules opened this issue Jun 2, 2016 · 4 comments
Closed

Comments

@PikaRules
Copy link

PikaRules commented Jun 2, 2016

Description

when EarlGrey tries to open a viewController where the MFMailComposeViewController has been initialized, many warning messages start being printed on the console. and earlgrey keeps waiting forever until the test is marked as failed.

The warning message is:

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

observations:

If you turn off synchronization the test continues until it finish, which marks the test as success. but the warning messages keeps appearing.

@tirodkar
Copy link
Collaborator

tirodkar commented Jun 2, 2016

Based on looking around for this error, this looks like a Synchronization problem with the MFMailComposeViewController. Thanks for bringing this to our attention. Is there a simple way by which we could repro this?

@PikaRules
Copy link
Author

To reproduce it you just need to create an instance of MFMailComposeViewController on some ViewController and add it as a property of that ViewController, create that instance inside viewDidLoad()
the view controller needs to have some view attached to it.
and this view should have some accessibilityElements turned on with an accessibilityIdentifier settled.

then, create a simple test that opens that viewController

after that, the error posted above should appear in the console log of xcode.

@tirodkar
Copy link
Collaborator

tirodkar commented Sep 2, 2016

@PikaRules, was there any update on this from your side? Is it still present?

@khandpur
Copy link
Collaborator

Fixed by commit: 9744dfe

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants