Connection issue in React Native

Opened on behalf of @hdvreyes:

I can’t seem to establish a connection unless my debugger is on. Am running on “react-native”: “0.63.4” and “@stomp/stompjs”: “^6.0.0”. ` const client = Stomp.over(function() { return new SockJS(socketUrl); });

client.reconnectDelay = 10000; client.heartbeatIncoming = 5000; client.heartbeatOutgoing = 5000; client.forceBinaryWSFrames = true; client.appendMissingNULLonIncoming = true;

 client.connect(headers, () => {
    client.subscribe(topic, callback, headers);
  });

` Has anyone encountered the same issue? thanks!

[kum-deepak]

Usually, it happens because of missing polyfills. This is a peculiar issue, in debug mode, React Native uses a full browser which is not the case in production mode. That causes the list of polyfills to be different in both modes. Please see https://stomp-js.github.io/guide/stompjs/rx-stomp/ng2-stompjs/pollyfils-for-stompjs-v5.html#in-react-native

Few topics related to React Native has been compiled at https://stomp-js.github.io/workaround/stompjs/rx-stomp/ng2-stompjs/react-native-additional-notes.html

Please let me know if it helps.

In addition, Stomp.over and client.connect are v4 syntax and are available as compatibility, i.e., mixing of newer features may not work. Please see https://stomp-js.github.io/#upgrading and https://stomp-js.github.io/#getting-started.

[kum-deepak]

I am sorry, I am unable to suggest anything more than https://stomp-js.github.io/workaround/stompjs/rx-stomp/ng2-stompjs/react-native-additional-notes.html. Please try the first approach. It may not help, but try adding client.forceBinaryWSFrames = true;