-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Add WebSocket support for the iOS #1894
Comments
Hi @Hixie, the WebSocket is unsupported on the iOS for now. |
Hello, any update on this? I notice there's a PR that got stale #1535 |
I tried to use that code and it worked up to the point where I got another error
|
Hi @Hixie, the fix is in the master for the nonce class, but there is no WebSocket support for ktor-ios. |
Hi @e5l, Yes you're right, I noticed it after reading the code, even tho the |
@e5l so latest ktor 1.3.2 still don't have websocket implementation on the IOS? |
Yep. We're waiting for |
Looks like native multithreaded support almost here :) |
Weirdly, I am getting this exception ( Digging into Kotlin Native code, I guess POSIX in general is not supported |
Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks. |
@e5l Hey, any updates on this? |
@e5l yes, please update, we are so excited about websocket support for iOS! |
Hi! Any news? Websocket support for iOS (namely for KMM) is really very necessary. Looking forward! |
Sorry for making this kind of comment, but is there an update on this? :) |
This feature (KTOR-4093) is already implemented. |
@Stexxe any progress on TLS for websocket? |
@ln-12 Thank you, will try |
This lib is just a magic - https://github.com/TheArchitect123/TitanSocket. Works on iOS + Android from the box |
Ktor Version and Engine Used (client or server and name)
Using
io.ktor:ktor-client-ios:1.3.2
Describe the bug
This code prints
kotlin.IllegalStateException: [generateNonce] is not supported on iOS
:Looks like someone tried to fix this here: #1535
The text was updated successfully, but these errors were encountered: