Can not subscribe to channel from NodeJS

Serge_Zenchenko · March 18, 2019, 7:54am

Hi,

I’m getting the error {“type”:“TransportError”,“description”: 503}, while trying to connect to channel.

Also tried using REST and in web, and everything works.

Code:
const Backendless = require(‘backendless’);

Backendless.initApp(process.env.APP_ID, process.env.JS_KEY);

const channel = Backendless.Messaging.subscribe(‘default’);
channel.addMessageListener(console.log);

Node - v8
Backendless - latest

Volodymyr_Ialovyi · March 18, 2019, 8:17am

Hi @Serge_Zenchenko

On which line does the error message appear?

Serge_Zenchenko · March 18, 2019, 8:37am

Hi, on line 5.

I think the error is occurred, while socket handshaking.

Volodymyr_Ialovyi · March 18, 2019, 8:45am

You have
function onMessage (message) { console.log (“Message received:” + message) }
as described here - https://backendless.com/docs/js/pubsub_subscription_introduction.html ?

Can you run in debug mode and see where the error occurs?

Serge_Zenchenko · March 18, 2019, 9:05am

Even if you will delete the message listener, you will get the error, which is thrown by socket.io, while trying to handshake.

One of the SDK dependencies is backendless-rt-client, which is establishing socket connection with Backendless.

In backendless-rt-client check src/socket.js, the error is logged (not thrown) from there, line 98.

vladimir-upirov · March 18, 2019, 10:01am

Hi @Serge_Zenchenko
the issue has been solved, could you confirm it please?
Regards, Vlad

Serge_Zenchenko · March 18, 2019, 10:05am

Hi @vladimir-upirov,

Yes, it works now. Thanks.

Enrique_Diaz · June 25, 2019, 2:53am

Hi @vladimir-upirov,

I’m having the exact same issue with the SDK version 5.2.13.
I notice a GET request being repeteadly invoked ( /rt/lookup ) which doesn’t return error code but 200 and a response like “https://rt-app#.backendless.com:50010”.

Publish API seems to work properly though.

vladimir-upirov · June 25, 2019, 7:03am

Hi @Enrique_Diaz

I just checked it, and looks like there are not any issue, everything works well

add a simple code into “./server/index.js” file :

 const Backendless = require('backendless');

 Backendless.initApp('YOUR_APP_ID', 'YOUR_JS_API_KEY');

 const channel = Backendless.Messaging.subscribe('default');

 channel.addMessageListener(message => console.log('message:', message));

run it: node server
publish a new message, and in terminal output the new messages appear

could you please provide steps to reproduce and env when do you run your code

Regards, Vlad

Enrique_Diaz · June 25, 2019, 11:29pm

Sure, I’ll try to be as specific as possible. My project is based on Angular 7 + Ionic 4.

The MessagingService provides a function to post and subscribe to channels.
import {Injectable} from ‘@angular/core’;
import * as Backendless from ‘backendless’;

@Injectable({
    providedIn: 'root'
})
export class MessagingService {

    public getConversationChannel(channelId): Backendless.ChannelClass {
        return Backendless.Messaging.subscribe(channelId);
    }

    public postMessage(message) {
        return Backendless.Messaging.publish('default', message);
    }
}

At my page/component layer, only 2 buttons are displayed: Join (subscribes to a channel [NOT WORKING]) and Post (posts into the channel).

<ion-header>
    <ion-toolbar>
        <ion-title>Chat</ion-title>
        <ion-buttons slot="start">
            <ion-back-button defaultHref="/"></ion-back-button>
        </ion-buttons>
    </ion-toolbar>
</ion-header>

<ion-content>
    <button (click)="initChannel()">JOIN</button>
    <button (click)="postMessage()">POST</button>
</ion-content>

The TypeScript functions:

    private conversationChannel;
    initChannel() {
           this.conversationChannel = this.messagingService.getConversationChannel('default');
        console.log(this.conversationChannel);

        this.conversationChannel.addMessageListener((message) => {
            console.log('RT Received: ', message);
        });
    }

    postMessage() {
        this.messagingService.postMessage('hello world!');
    }

Check what’s happening (I’ll attach to this reply some screenshots [I tried but not granted due to “new user”. Sorry about that]):

Open the Chat page.
Click on the JOIN button. Tries to subscribe doesn’t join to the channel. The /lookup API request starts to be invoked infinitely.
Verified the channel subscription state: Not joined.
Click the POST button and successfully posts the message. Verified in Backendless console.

I assume I’m missing something, but cannot mind what.
Thanks in advance!

vladimir-upirov · June 26, 2019, 7:48am

actually, the topic title says that issue is in NodeJS env, but you’ve got a problem in Ionic env, so it’s a little different problem

anyways, let’s try to figure out what’s going on here

could you please archive your project (or create another one with minimal code) for reproduce the problem and send it to us support@backendless.com, also please attach instruction how to install/run the app and we will take a look at the issue

and also you can try to enable debug mode, for that just add the next line right after Backendless.initApp(…)
Backendless.debugMode = true
maybe, there will be some helpful info

Regards, Vlad

Enrique_Diaz · June 26, 2019, 1:53pm

I assumed that Backendless JS SDK worked the same for NodeJS, Angular, etc.

I’ll make a small project including what you request and be in touch!
Thanks

Enrique_Diaz · August 4, 2019, 6:12pm

Hi @vladimir-upirov,
I sent an email to support@backendless.com on July 18th but I haven’t received any response yet. Is there any update regarding my ticket?

Thanks.

vladimir-upirov · August 19, 2019, 10:53am

Hello @Enrique_Diaz
Sorry for the late response,
I’ve found the problem, the issue is with Angular and SocketIO library which is used in our JS-SDK

github.com/socketio/socket.io-client

Library socket.io-client is not compatible with latest Angular 6

opened 11:29AM - 13 May 18 UTC

closed 12:09PM - 17 Dec 20 UTC

jameskentTX

bug

### I want to: * [x] report a *bug* - solved, look last two lines for workar…ound Library socket.io-client is not compatible with latest Angular 6. There is error at execution time: ReferenceError: global is not defined at Object../node_modules/socket.io-client/node_modules/socket.io-parser/is-buffer.js (is-buffer.js:4) Please read comment below to know more: https://github.com/angular/angular-cli/issues/9827#issuecomment-369578814 If you want to see this error for yourself, add to angular 6.0 app simple service like that below: ```js import { Injectable } from 'angular/core'; import * as socketIo from 'socket.io-client'; @Injectable() export class SocketService { private socket; constructor() {} public initSocket(): void { this.socket = socketIo(); } } ``` Error disappears when you remove initSocket function. ******************************************************************************** ******************************************************************************** Ok, there is workaround in Angular 6 to work with socket.io-client. Add (window as any).global = window; to polyfills.ts

the latest comment looks like fixes the problem, just add the following line in …/src/polyfills.ts file

(window as any).global = window;

Regards, Vlad

Enrique_Diaz · September 11, 2019, 4:02am

Hi,

Thank you so much for the response. I applied the suggested workaround and it does work now as expected.

Regards!

Iain_Todd · April 13, 2020, 3:37am

Hi there,

I have the same issue in an Angular app where I am not receiving any messages.

The message is published (can see it in the backendless dashboard) but the message listener never receives it. There is no console error and I’ve tried the polyfill fix but no luck.

Any ideas or help would be great.
Thanks,
Iain

Angular: 9.0.7
backendless: 5.8.8

vladimir-upirov · April 13, 2020, 6:34am

Hello @Iain_Todd

try to add the following code right after Backendless.initApp to check the JS-SDK able to connect to RT-Server

Backendless.RT.addConnectErrorEventListener((...args) => console.log('addConnectErrorEventListener', ...args));
Backendless.RT.addConnectEventListener((...args) => console.log('addConnectEventListener', ...args));
Backendless.RT.addDisconnectEventListener((...args) => console.log('addDisconnectEventListener', ...args));
Backendless.RT.addReconnectAttemptEventListener((...args) => console.log('addReconnectAttemptEventListener', ...args));

Regards, Vlad

Iain_Todd · April 13, 2020, 7:42am

Thanks for the responsive reply @vladimir-upirov,
I’m seeing this in the console now…

addConnectErrorEventListener Cannot read property 'Blob' of undefined
addReconnectAttemptEventListener 1 400
addConnectErrorEventListener io is not a function
addReconnectAttemptEventListener 2 400
addConnectErrorEventListener io is not a function
addReconnectAttemptEventListener 3 400
addConnectErrorEventListener io is not a function
etc...

vladimir-upirov · April 13, 2020, 7:44am

it seems like it’s related to Backendless RT not working for me in JS SDK

vladimir-upirov · April 13, 2020, 12:44pm

we will investigate it and notify you about any result asap