2016-10-18 17:26:28.399 iOS Example[62704:1929149] AUTO: did set active transport to webSockets
However when we have a cookie in the request, we get the following:
2016-10-18 17:50:50.767 iOS Example[67514:1966092] WS: websocket will connect with connectionData [{"Name":"apphub"}]
2016-10-18 17:50:50.767 FStiOS Examplep[67514:1966092] WS: websocket will connect at url: https://app.azurewebsites.net/signalr/connect?connectionData=%5B%7B%22Name%22%3A%22apphub%22%7D%5D&connectionToken=8pldVoJOzAKgTFlTMGm/y%2Bh1RXhgLw99RU/nSs6cYGPZPT3PZQT7K77FMoRaLUvsHzLvLKUaMjoBfKWrhka00VHc70N7GjqMpXtdw0rFVEIP%2Bk5C&groupsToken=&messageId=&transport=webSockets&username=bob
Browse: Fetched
Me: Fetched => [Auth: 13076 | bob | Photographer] [Profile: 13076 | bob | Photographer]
Notifications: Fetching
2016-10-18 17:50:51.539 iOS Example[67514:1966092] WS: websocket did fail with error ebbee68a-0972-4722-b3ef-321beb81f143, Error Domain=SRWebSocketErrorDomain Code=2132 "received bad response code from server 403" UserInfo={NSLocalizedDescription=received bad response code from server 403, HTTPResponseStatusCode=403}
2016-10-18 17:50:51.539 iOS Example[67514:1966092] WS: websocket did fail while connecting
2016-10-18 17:50:51.540 iOS Example[67514:1966092] AUTO: will switch to next transport
2016-10-18 17:50:51.540 iOS Example[67514:1966092] AUTO: autoTransport will attempt to start serverSentEvents
What's notable is that the web app is working fine. The AppHub serverside does not Authenticate, so I don't know why we would be getting forbidden here.
We have an implementation of SignalR that is working perfectly fine with a Web application. When trying to use this with a native app:
When we're not logged in (no cookie), we get:
2016-10-18 17:26:28.399 iOS Example[62704:1929149] AUTO: did set active transport to webSockets
However when we have a cookie in the request, we get the following:
What's notable is that the web app is working fine. The AppHub serverside does not Authenticate, so I don't know why we would be getting
forbidden
here.