-
Notifications
You must be signed in to change notification settings - Fork 69
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
Connect / contentsOfDirectoryAtPath fail on Xcode10.2.1 (iOS 11/12) #28
Comments
Please run tests on your computer. You must change server address and share name in tests. |
Also...how is possibile that with the same code on Xcode10.1 works perfectly and with latest version all is broken? |
It's not about believing or not, I should be able to reproduce the exact issue in order to debug. Please create a sample project at least. |
I prepared a sample and systematically every time timeout expires I get Thanks so much |
Any news? |
I have the same problem. However, the problem does not appear to be in |
@emilhornlund that's very interesting, what's your environment? Xcode/iOS version? |
macOS 10.14.5, Xcode 10.2.1, Simulator 12.2, iPhone 12.1.2 |
i'll try it out |
@emilhornlund i have some updates:
I tried samba server hosted on macOS 10.14, and 10.13 no difference. |
Hi, I'm busy on deadlines right now. I shall investigate but it appears it is an issue in Swift runtime on specific version. |
I have the same problem, crash happens in any possible situation, not just in simulator or specific macOS version. Is there a solution? |
The method while connecting or trying to get contents listing (I assume because it's never reached), hangs...and after a very long timeout no completion is called and nothing is returned. If in my code a execute again it crashes on
bindMemory
method.How can I solve? I need latest Xcode version to support iOS12.
I already updated to latest (2.0) git release
Tested on with Xcode 10.1 (AMSMB v1.7.0) everything works. I cannot test the latest due to swift 5.0 compatibility
The text was updated successfully, but these errors were encountered: