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

Bad File Descriptor crash SelectorEventLoop Xcode 14 #104

Open
danielbowden opened this issue Oct 28, 2022 · 4 comments
Open

Bad File Descriptor crash SelectorEventLoop Xcode 14 #104

danielbowden opened this issue Oct 28, 2022 · 4 comments

Comments

@danielbowden
Copy link

danielbowden commented Oct 28, 2022

Hi, v4.1.4 resolved the memoryRebound fatal error on Xcode 14 / iOS 16 that we were seeing but there is also another issue in SelectorEventLoop.

Embassy/SelectorEventLoop.swift:88: Fatal error: 'try!' expression unexpectedly raised an error: Embassy.OSError.ioError(number: 9, message: "Bad file descriptor")
2022-10-28 01:08:39.731236+1100 XYZUITests-Runner[81238:5120563] Embassy/SelectorEventLoop.swift:88: Fatal error: 'try!' expression unexpectedly raised an error: Embassy.OSError.ioError(number: 9, message: "Bad file descriptor")

Screen Shot 2022-10-29 at 1 22 40 am

This looks like it was also raised in envoy/Ambassador#67 but I thought I'd add it here for more visibility.

We've tried cleaning up the event loop vars between tests, sharing a single instance of the server, and various other tweaks but no luck. Our use of Embassy is an almost identical setup to described here: https://envoy.engineering/embedded-web-server-for-ios-ui-testing-8ff3cef513df#.c2i5tx380

Any help or ideas would be appreciated.

Xcode 4.0.1
Embassy 4.1.4
macOS 12.6
Simulator iOS 16.0

@D3icidal
Copy link

D3icidal commented Dec 5, 2022

Where you able to find a workaround?

@jmortimer13
Copy link

We are seeing this crash in our projects after upgrading to Xcode 14, no workaround found yet.

@weibel
Copy link

weibel commented Jan 13, 2023

We're seeing a similar exception in line 80
If it's known those methods can throw why not make the containing func throwing and pass the exception up to the user of the lib?

@weibel
Copy link

weibel commented Jan 30, 2023

Our issue seems to have been fixed with #105

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

No branches or pull requests

4 participants