ASP.NET Core 2.2 - Mobile Browsers Not Closing Web Socket
I have a server deployed that is using Web Sockets for real time communications with clients. I'm finding that if a client is using Safari on an iOS device and the app goes into a background state or if they sleep the screen it will break the Web Socket connection (stopping any comms after going back to Safari), but on the server side it is not invoking the OnDisconnected event.
I only found this because I was tracking how many connected users I have and it just continually rises.
Chrome, Firefox, and Edge all work as expected on a desktop PC and they invoke the OnDisconnected event.
I was wondering if anyone has seen this before, if I'm missing a setting, or if there is a work around? So far, in my method that sends data to clients, I check all cached sockets to see if they are not in the "Open" state, and manually force them closed.
ios c# asp.net websocket
asked Jan 25 at 21:31
BagoetteBagoette
11
add a comment |
I have a server deployed that is using Web Sockets for real time communications with clients. I'm finding that if a client is using Safari on an iOS device and the app goes into a background state or if they sleep the screen it will break the Web Socket connection (stopping any comms after going back to Safari), but on the server side it is not invoking the OnDisconnected event.
I only found this because I was tracking how many connected users I have and it just continually rises.
Chrome, Firefox, and Edge all work as expected on a desktop PC and they invoke the OnDisconnected event.
I was wondering if anyone has seen this before, if I'm missing a setting, or if there is a work around? So far, in my method that sends data to clients, I check all cached sockets to see if they are not in the "Open" state, and manually force them closed.
ios c# asp.net websocket
asked Jan 25 at 21:31
BagoetteBagoette
11
[2019-01-27 05:32:38] Connection id "0HLK44LQK6LG8", Request id "0HLK44LQK6LG8:0000002F": An unhandled exception was thrown by the application. This is occuring every time a mobile browser goes to a sleep state. I don't know how to track where it's coming from, and the server doesn't seem to be crashing just logging this error.
– Bagoette
Jan 28 at 0:15
add a comment |
I have a server deployed that is using Web Sockets for real time communications with clients. I'm finding that if a client is using Safari on an iOS device and the app goes into a background state or if they sleep the screen it will break the Web Socket connection (stopping any comms after going back to Safari), but on the server side it is not invoking the OnDisconnected event.
I only found this because I was tracking how many connected users I have and it just continually rises.
Chrome, Firefox, and Edge all work as expected on a desktop PC and they invoke the OnDisconnected event.
I was wondering if anyone has seen this before, if I'm missing a setting, or if there is a work around? So far, in my method that sends data to clients, I check all cached sockets to see if they are not in the "Open" state, and manually force them closed.
ios c# asp.net websocket
asked Jan 25 at 21:31
BagoetteBagoette
11
I have a server deployed that is using Web Sockets for real time communications with clients. I'm finding that if a client is using Safari on an iOS device and the app goes into a background state or if they sleep the screen it will break the Web Socket connection (stopping any comms after going back to Safari), but on the server side it is not invoking the OnDisconnected event.
I only found this because I was tracking how many connected users I have and it just continually rises.
Chrome, Firefox, and Edge all work as expected on a desktop PC and they invoke the OnDisconnected event.
I was wondering if anyone has seen this before, if I'm missing a setting, or if there is a work around? So far, in my method that sends data to clients, I check all cached sockets to see if they are not in the "Open" state, and manually force them closed.
ios c# asp.net websocket
ios c# asp.net websocket
asked Jan 25 at 21:31
BagoetteBagoette
11
asked Jan 25 at 21:31
BagoetteBagoette
11
asked Jan 25 at 21:31
BagoetteBagoette
11
asked Jan 25 at 21:31
BagoetteBagoette
11
asked Jan 25 at 21:31
BagoetteBagoette
11
11
[2019-01-27 05:32:38] Connection id "0HLK44LQK6LG8", Request id "0HLK44LQK6LG8:0000002F": An unhandled exception was thrown by the application. This is occuring every time a mobile browser goes to a sleep state. I don't know how to track where it's coming from, and the server doesn't seem to be crashing just logging this error.
– Bagoette
Jan 28 at 0:15
add a comment |
[2019-01-27 05:32:38] Connection id "0HLK44LQK6LG8", Request id "0HLK44LQK6LG8:0000002F": An unhandled exception was thrown by the application. This is occuring every time a mobile browser goes to a sleep state. I don't know how to track where it's coming from, and the server doesn't seem to be crashing just logging this error.
– Bagoette
Jan 28 at 0:15
[2019-01-27 05:32:38] Connection id "0HLK44LQK6LG8", Request id "0HLK44LQK6LG8:0000002F": An unhandled exception was thrown by the application. This is occuring every time a mobile browser goes to a sleep state. I don't know how to track where it's coming from, and the server doesn't seem to be crashing just logging this error.
– Bagoette
Jan 28 at 0:15
[2019-01-27 05:32:38] Connection id "0HLK44LQK6LG8", Request id "0HLK44LQK6LG8:0000002F": An unhandled exception was thrown by the application. This is occuring every time a mobile browser goes to a sleep state. I don't know how to track where it's coming from, and the server doesn't seem to be crashing just logging this error.
– Bagoette
Jan 28 at 0:15
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1398578%2fasp-net-core-2-2-mobile-browsers-not-closing-web-socket%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1398578%2fasp-net-core-2-2-mobile-browsers-not-closing-web-socket%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
[2019-01-27 05:32:38] Connection id "0HLK44LQK6LG8", Request id "0HLK44LQK6LG8:0000002F": An unhandled exception was thrown by the application. This is occuring every time a mobile browser goes to a sleep state. I don't know how to track where it's coming from, and the server doesn't seem to be crashing just logging this error.
– Bagoette
Jan 28 at 0:15