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
Error: Optional(["message": Error during negotiation request.]) #75
Comments
Does it work with If so, make sure you have CORS enabled on your server. CORS is required for WKWebView to work with SwiftR. |
Having same issue. Help us to fix this. |
@tejasverixo Please answer same questions RE: wkWebView = false, and whether or not CORS is enabled on your SignalR server. |
Thanks for quick reply. But i got solution. By default SwiftR.useWKWebView = false - It's working fine. //As per the "Master" branch update i m getting following error //Code //Error Note: I did Installation using Pod I have posted the full question here in stackoverflow. |
@tejasverixo I posted this on SO, but will paste here too: The pod (swift3), the swift23 branch, and the master branch (API changes) are all different code. You'll need to pick one version of the library and stick with it. If WKWebView = false works, but true doesn't, that means you probably don't have CORS enabled on your SignalR server. CORS is most likely the culprit here. |
hey im having same issue. when i false SwiftR.useWKWebView it, server responding with this error |
Hi I am trying to use swiftR , i don't know anything about this, I do not chat application. I don't know where should call server method from client and send parameter to server, or call client method from server and send JSON to client. please help me to fix this, thanks. |
Anyone having the same issue now that UIWebView is not available ? |
Hi iam trying to connect to Hub. But getting the error like this
I have posted the full question here in stackoverflow.
http://stackoverflow.com/questions/41162408/signal-r-in-swift
Can you please help me to fix this.
The text was updated successfully, but these errors were encountered: