SignalR does not work for .net core - react template

I am using Abp.AspNetCode 4.9.0 with react template. Under App.tsx there is a signalR initialization code piece

if (!!this.props.sessionStore!.currentLogin.user && 
    this.props.sessionStore!.currentLogin.application.features['SignalR']) {
if (this.props.sessionStore!.currentLogin.application.features['SignalR.AspNetCore']) {
    SignalRAspNetCoreHelper.initSignalR();
}

So I provided “SignalR” and “SignalR.AspNetCore” features to the related login. And when the code gets executed I am seeing following error from the file signalRAspNetCoreHelper.ts

Util.loadScript(AppConsts.appBaseUrl + '/dist/abp.signalr-client.js');

dist/abp.signalr-client.js:1 - Uncaught SyntaxError: Unexpected token ‘<’

That’s because script loading from /dist/abp.signalr-client.js returns a regular 404 page.

Also when I load abp.signalr-client.js as a class manually, the signalR variable is undefined so the code does not work.

Could you help me with bringing SignalR up for the react template?

[kwstasarva]

@cokceken Hi,

The issue is cause from the SignalRAspNetCoreHelper.ts line 18.

Util.loadScript(AppConsts.appBaseUrl + '/dist/abp.signalr-client.js');

The code tries to load a file from localhost:3000/dist/abp.signalr-client.js and fails to do so. The reason behind it is because, such URL does not exist.

In order to fix the issue for the development environment you should modify the craco.config.js in line 44 and include the following piece of code to:'dist/abp.signalr-client.js'

Please find my full craco.config.js file below for reference.

craco.config.js.zip

Haven’t tested my change in the production environment but I am pretty sure that you should follow the same approach.

After making that change, the error should now be gone. Enjoy.

[maliming]

@kwstasarva 💯 I will update the template.