Signalr: XML parsing error: Hub reply does not define a root element
I'm replicating the issue reported in the SignalR Core repo
This doesn't present a problem of the function, it is just not pretty; when invoking a method on the server my FF Developer tab reports:
XML Parsing Error: no root element found
Location: https://localhost:44311/signalr?id=ff8ff481-439a-4bcc-8f1f-67941a5ca331
Line Number 1, Column 1:
Again, not a bug per se but it does clutter the dev window. Not sure if it can be changed or if the browser is wrong.
I'm getting the same issue on FF when SignalR calls the close function. I'm getting this when the page is unloaded. It's not a big deal, but nobody like getting errors on the dev tools.
kblok
All 9 comments
I'm experiencing the same issue.
isaacplmann
on 15 Feb 2018
Having the same issue too...
Nath0s
on 16 Feb 2018
Same here. It seemed to not be this way not but yesterday. Then I changed my hubs to reduce the number of methods. In fact, eliminating all methods because only want to emit events.
I tried adding methods, to see if the XML changed, but no dice.
electricessence
on 16 Feb 2018
Using .NET MVC SIGNALR and jquery signalR 2.2.2 and, in firefox, getting following in console...
XML Parsing Error: no root element found
Location: http://l-mmoloney2.qvidiancorp.com/Qvidian.WOPI/signalr/signalr/abort?transport=we.......
This seems to then stop any SIGNALR messaging for the browser.
Is there a new release upcoming to fix this?
molo9966
on 23 Feb 2018
2.2.3 - same issue. It seems like SignalR for asp.net is a forgotten project...
omaximenco
on 17 Apr 2018
@omaximenco It's definitely not forgotten. It's in NPM without jQuery. As the new Core version.
The issue is kinda jQuery because a request without a response body is fine, but only works without throwing in jQuery if you specify the content to be text and not json. :(
electricessence
on 17 Apr 2018
@molo9966 Apparently, firefox is losing the connection right after the first connection attempt, the only fix i found was to call the connection function after the disconnection is detected
//Only for firefox
$.connection.hub.disconnected(function () {
setTimeout(function () {
$.connection.hub.start().done(function () {
});
}, 1);
});
With this it should be alright ;)
Nath0s
on 18 Apr 2018
lol I think the right fix is not to use jQuery (which is exactly how the new signalR works). But again, if jquery for this version is a must, then the underlying request needs to specify the expected return type as text if no data is to be returned and only a 200.
electricessence
on 18 Apr 2018
This was fixed in https://github.com/SignalR/SignalR/commit/a0b4b4b74ce35d9359182ad654c8c9453e06685f
anurse
on 11 Oct 2018
Related issues
ghost
·
3Comments
DOMZE
·
4Comments
cceraja
·
6Comments
thedutchess
·
4Comments
Vaccano
·
5Comments
Most helpful comment
This was fixed in https://github.com/SignalR/SignalR/commit/a0b4b4b74ce35d9359182ad654c8c9453e06685f