Unrecognized WebSocket connection option(s) `agent`, `perMessageDeflate`, `pfx`, `key`, `passphrase`, `cert`, `ca`, `ciphers`, `rejectUnauthorized`. Did you mean to put these under `headers`? #1290

JuAlexandre · 2019-04-15T12:30:39Z

You want to:

report a bug
request a feature

Current behaviour

When I install socket.io-client on a blank React Native Expo project I have a yellow message with:

Unrecognized WebSocket connection option(s) `agent`, `perMessageDeflate`, `pfx`, `key`, `passphrase`, `cert`, `ca`, `ciphers`, `rejectUnauthorized`. Did you mean to put these under `headers`?

Steps to reproduce (if the current behaviour is a bug)

yarn add socket.io-client

In App.js in the React Native project:

import React from 'react';
import { YellowBox } from 'react-native';
import io from 'socket.io-client';

YellowBox.ignoreWarnings(['Remote debugger']);

import AppContainer from './config/routing';

export default class App extends React.Component {
    constructor(props) {
        super(props);
    }

    componentWillMount() {
        const socket = io('http://10.0.60.26:3000', {
            forceNew: true
        });
        socket.on('connect', () => console.log('Connection'));
    }

    render() {
        return <AppContainer />;
    }
}

The text was updated successfully, but these errors were encountered:

bogoslavskiy · 2019-04-21T13:18:28Z

Same problem :(

Luomusha · 2019-04-23T15:13:39Z

+1

evaleirasclapps · 2019-05-06T18:12:22Z

+1

nsafai · 2019-05-07T02:59:03Z

+1

Seems to have been an issue since at least as far back as Dec 18

hbouhadji · 2019-05-09T09:56:58Z

+1

wx962464 · 2019-05-22T02:13:02Z

+1

maxgfr · 2019-07-01T11:16:30Z

+1

vietmobilefolk · 2019-07-04T14:10:12Z

+1

marcinczenko · 2019-07-08T13:10:27Z

I am still getting this warning when using socket.io (2.2.0) on React-Native. I can silence the yellow box on the device screen with:

import { YellowBox } from 'react-native'

YellowBox.ignoreWarnings([
  'Unrecognized WebSocket connection option(s) `agent`, `perMessageDeflate`, `pfx`, `key`, `passphrase`, `cert`, `ca`, `ciphers`, `rejectUnauthorized`. Did you mean to put these under `headers`?'
])

but I still get this annoying warning on the console...

samuelgoldenbaum · 2019-08-08T23:55:22Z

downgrade to "socket.io-client": "2.1.0" and all OK

litsdm · 2019-08-13T17:50:39Z

For me it worked when I downgraded to 2.1.1 I did:
yarn add socket.io-client@2.1.1

At first it didn't work because I was adding the ^ symbol before the version socket.io-client@^2.1.1 which I believe accepts other minor versions of the package.

FrederickEngelhardt · 2019-08-15T02:44:53Z

Still an issue @2.2.0

AminHwadria · 2019-09-04T15:58:11Z

Try downgrading socket.io-client to 1.7.2, it works for me.

Andrielson · 2019-10-04T18:22:29Z

Still an issue @^2.3.0

ghost · 2019-10-18T06:25:26Z

Still an issue v2.3.0 with react-native

emclab · 2019-10-18T07:51:55Z

@2.1.1 is OK. But 2.3.0 throws the warning message on RN 0.61.1

ashadnasim52 · 2019-10-22T11:48:52Z

any solution till now

jhoanborges · 2019-10-29T21:27:26Z

Still an issue v2.3.0 with react-native

canaanites · 2019-10-29T21:38:54Z

Hey guys! We have fixed this issue by downgrading to v2.1.1

Make sure you completely remove the older version and clear the cache.

remove socket.io-client from package.json & better delete your package-lock/yarn.lock files.
delete your entire node_modules folder (start fresh)
npm install socket.io-client@2.1.1 --save

Done! This should work with react-native & react-native-web!

jeanlambert17 · 2019-11-14T15:01:40Z

I have this same issue with react-native: 0.61.4 but somehow the app is crashing, I don't know if it's happening because of the warning or if is another socket-related thing, but when I tried to connect to the socket the app closes.

This is my conf:
{ autoConnect: false, reconnectionDelay: 1000, reconnection: true, transports: ['websocket'], agent: false, // [2] Please don't set this to true upgrade: false, rejectUnauthorized: false }

jeanlambert17 · 2019-11-14T21:18:06Z

Does socket.open crashes if the socket is already connected?

peterboyer · 2019-11-20T05:31:04Z

This warning is raised here by ReactNative/WebSocket.js:117 because EngineIO (used by SocketIO under the hood) will reference the exposed ReactNative WebSocket implementation via EngineIO/websocket.js:121 which is passed opts which contains the properties that the warning message mentions. Curiously enough, these added properties described by the EngineIO maintainers via comment are "SSL options for Node.js client".

By inserting something like the code below at EngineIO/websocket.js:114 to manipulate the opts given to the WebSocket constructor we remove all the extraneous keys in opts to successfully stop the warning from appearing in the first place (omit is imported from Lodash, can be reworked out).

// lib/transports/websocket.js
...
if (this.isReactNative) {
  // prettier-ignore
  opts = omit(opts, ['agent', 'perMessageDeflate', 'pfx', 'key', 'passphrase', 'cert', 'ca', 'ciphers', 'rejectUnauthorized']);
}
...

If you're looking for a solution that doesn't involve simply muting the warning via YellowBox.ignoreWarnings then you could completely override the doOpen as defined EngineIO/websocket.js:87 by adding something like this below, to the entry point of your ReactNative project, typically index.js.

// index.js
...
+ import 'patches/EngineIOHeaderWarning';
...

// patches/EngineIOHeaderWarning.js
const WS = require('engine.io-client/lib/transports/websocket');

var WebSocketImpl = WebSocket; // eslint-disable-line no-undef

WS.prototype.doOpen = function() {
  if (!this.check()) {
    // let probe timeout
    return;
  }

  var uri = this.uri();
  var protocols = this.protocols;
  var opts = {};

  if (this.extraHeaders) {
    opts.headers = this.extraHeaders;
  }
  if (this.localAddress) {
    opts.localAddress = this.localAddress;
  }

  try {
    this.ws = new WebSocketImpl(uri, protocols, opts);
  } catch (err) {
    return this.emit('error', err);
  }
};

Overall, if we create a pull request for EngineIO to exclude these extra opts that aren't needed when used in ReactNative via this.isReactNative then we could suppress this warning for all using the SocketIO Client in their ReactNative projects.

jzambrano12 · 2020-01-27T23:04:16Z

You want to:

report a bug
request a feature

Current behaviour

When I install socket.io-client on a blank React Native Expo project I have a yellow message with:

Unrecognized WebSocket connection option(s) `agent`, `perMessageDeflate`, `pfx`, `key`, `passphrase`, `cert`, `ca`, `ciphers`, `rejectUnauthorized`. Did you mean to put these under `headers`?

Steps to reproduce (if the current behaviour is a bug)

yarn add socket.io-client

In App.js in the React Native project:

import React from 'react';
import { YellowBox } from 'react-native';
import io from 'socket.io-client';

YellowBox.ignoreWarnings(['Remote debugger']);

import AppContainer from './config/routing';

export default class App extends React.Component {
    constructor(props) {
        super(props);
    }

    componentWillMount() {
        const socket = io('http://10.0.60.26:3000', {
            forceNew: true
        });
        socket.on('connect', () => console.log('Connection'));
    }

    render() {
        return <AppContainer />;
    }
}

My Solution:

Just save the socket in a useState like this:

import io from 'socket.io-client';
// ...

const [socket] = useState(() => io('SERVER_URL'));

Problem solved.

prettydev · 2020-02-01T00:32:11Z

In my case, v2.3 is ok when I connect to the local socket.io server.
But it occurs errors when I connect to the remote socket.io server.
The server source is the same.
So I downgrade the socket.io client version to 2.1.1, and it works fine.

JamesMahy · 2020-02-02T10:37:47Z

This warning is raised here by ReactNative/WebSocket.js:117 because EngineIO (used by SocketIO under the hood) will reference the exposed ReactNative WebSocket implementation via EngineIO/websocket.js:121 which is passed opts which contains the properties that the warning message mentions. Curiously enough, these added properties described by the EngineIO maintainers via comment are "SSL options for Node.js client".

By inserting something like the code below at EngineIO/websocket.js:114 to manipulate the opts given to the WebSocket constructor we remove all the extraneous keys in opts to successfully stop the warning from appearing in the first place (omit is imported from Lodash, can be reworked out).
// lib/transports/websocket.js
...
if (this.isReactNative) {
  // prettier-ignore
  opts = omit(opts, ['agent', 'perMessageDeflate', 'pfx', 'key', 'passphrase', 'cert', 'ca', 'ciphers', 'rejectUnauthorized']);
}
...
If you're looking for a solution that doesn't involve simply muting the warning via YellowBox.ignoreWarnings then you could completely override the doOpen as defined EngineIO/websocket.js:87 by adding something like this below, to the entry point of your ReactNative project, typically index.js.
// index.js
...
+ import 'patches/EngineIOHeaderWarning';
...
// patches/EngineIOHeaderWarning.js
const WS = require('engine.io-client/lib/transports/websocket');

var WebSocketImpl = WebSocket; // eslint-disable-line no-undef

WS.prototype.doOpen = function() {
  if (!this.check()) {
    // let probe timeout
    return;
  }

  var uri = this.uri();
  var protocols = this.protocols;
  var opts = {};

  if (this.extraHeaders) {
    opts.headers = this.extraHeaders;
  }
  if (this.localAddress) {
    opts.localAddress = this.localAddress;
  }

  try {
    this.ws = new WebSocketImpl(uri, protocols, opts);
  } catch (err) {
    return this.emit('error', err);
  }
};
Overall, if we create a pull request for EngineIO to exclude these extra opts that aren't needed when used in ReactNative via this.isReactNative then we could suppress this warning for all using the SocketIO Client in their ReactNative projects.

Your code wouldn't allow me to connect to the server and changed the intended behaviour of EngineIO so I've just wrapped those options in an if statement but used the same patch mechanism you suggested

// patches/EngineIOHeaderWarning.js
const WS = require('engine.io-client/lib/transports/websocket');

var WebSocketImpl = WebSocket; // eslint-disable-line no-undef

WS.prototype.doOpen = function() {
    if (!this.check()) {
        // let probe timeout
        return;
    }

    var uri = this.uri();
    var protocols = this.protocols;
    var opts = {};

    if(!this.isReactNative){
        opts.agent = this.agent;
        opts.perMessageDeflate = this.perMessageDeflate;

        // SSL options for Node.js client
        opts.pfx = this.pfx;
        opts.key = this.key;
        opts.passphrase = this.passphrase;
        opts.cert = this.cert;
        opts.ca = this.ca;
        opts.ciphers = this.ciphers;
        opts.rejectUnauthorized = this.rejectUnauthorized;
    }


    if (this.extraHeaders) {
        opts.headers = this.extraHeaders;
    }
    if (this.localAddress) {
        opts.localAddress = this.localAddress;
    }

    try {
        this.ws =
            this.usingBrowserWebSocket && !this.isReactNative
                ? protocols
                ? new WebSocketImpl(uri, protocols)
                : new WebSocketImpl(uri)
                : new WebSocketImpl(uri, protocols, opts);
    } catch (err) {
        return this.emit('error', err);
    }

    if (this.ws.binaryType === undefined) {
        this.supportsBinary = false;
    }

    if (this.ws.supports && this.ws.supports.binary) {
        this.supportsBinary = true;
        this.ws.binaryType = 'nodebuffer';
    } else {
        this.ws.binaryType = 'arraybuffer';
    }

    this.addEventListeners();
};

ioness · 2020-02-26T19:38:42Z

downgrade to "socket.io-client": "2.1.0" and all OK

This worked for me.

soullivaneuh · 2020-03-08T14:31:29Z

If I well understand the issue, is this a related dependencies issue introduce in 06e9a4c?

soullivaneuh · 2020-03-08T14:32:44Z

The downgrade to 2.1.1 works indeed, but we are stuck on a two years old releases.

Can @ptboyer be applied and release on the project?

schumannd · 2020-03-11T11:18:49Z

Does this warning affect the functionality of the package? Just setting it up and don't want to be held back by this. Happy to ignore if it has no other consequences

Edit: For anyone wondering the same thing. As far as I can tell this warning is inconsequential.

peterboyer · 2020-03-11T12:02:27Z

@schumannd This issue is purely about muting the error/warning message. Functionally, this warning is inconsequential. :)

MrCheater · 2020-03-12T10:45:04Z

+1

BassemN · 2020-03-12T10:50:30Z

I am very worried about if the socket.io library is still maintained or not because of no official reply about a fix or an upcoming update.

rburson · 2020-03-15T13:40:36Z

+1

rasoul707 · 2020-03-18T17:35:42Z

+1

isthaison · 2020-03-31T06:25:27Z

const _io = ioClient.connect(socketurl, { forceNode: true });
It's work

BassemN · 2020-03-31T08:06:19Z

@isthaison It doesn't work for me

marcorm · 2020-04-05T10:17:06Z

@isthaison for me it works... but every other http request becomes very slow... I don't know how it's related to the workaround... but it is...

dayaki · 2020-04-13T01:41:57Z

{ forceNode: true }

Thank you. this work for me.

BassemN · 2020-04-13T12:23:57Z

This is the only solution that worked for me.

This warning is raised here by ReactNative/WebSocket.js:117 because EngineIO (used by SocketIO under the hood) will reference the exposed ReactNative WebSocket implementation via EngineIO/websocket.js:121 which is passed opts which contains the properties that the warning message mentions. Curiously enough, these added properties described by the EngineIO maintainers via comment are "SSL options for Node.js client".
By inserting something like the code below at EngineIO/websocket.js:114 to manipulate the opts given to the WebSocket constructor we remove all the extraneous keys in opts to successfully stop the warning from appearing in the first place (omit is imported from Lodash, can be reworked out).
// lib/transports/websocket.js
...
if (this.isReactNative) {
  // prettier-ignore
  opts = omit(opts, ['agent', 'perMessageDeflate', 'pfx', 'key', 'passphrase', 'cert', 'ca', 'ciphers', 'rejectUnauthorized']);
}
...
If you're looking for a solution that doesn't involve simply muting the warning via YellowBox.ignoreWarnings then you could completely override the doOpen as defined EngineIO/websocket.js:87 by adding something like this below, to the entry point of your ReactNative project, typically index.js.
// index.js
...
+ import 'patches/EngineIOHeaderWarning';
...
// patches/EngineIOHeaderWarning.js
const WS = require('engine.io-client/lib/transports/websocket');

var WebSocketImpl = WebSocket; // eslint-disable-line no-undef

WS.prototype.doOpen = function() {
  if (!this.check()) {
    // let probe timeout
    return;
  }

  var uri = this.uri();
  var protocols = this.protocols;
  var opts = {};

  if (this.extraHeaders) {
    opts.headers = this.extraHeaders;
  }
  if (this.localAddress) {
    opts.localAddress = this.localAddress;
  }

  try {
    this.ws = new WebSocketImpl(uri, protocols, opts);
  } catch (err) {
    return this.emit('error', err);
  }
};
Overall, if we create a pull request for EngineIO to exclude these extra opts that aren't needed when used in ReactNative via this.isReactNative then we could suppress this warning for all using the SocketIO Client in their ReactNative projects.
Your code wouldn't allow me to connect to the server and changed the intended behaviour of EngineIO so I've just wrapped those options in an if statement but used the same patch mechanism you suggested
// patches/EngineIOHeaderWarning.js
const WS = require('engine.io-client/lib/transports/websocket');

var WebSocketImpl = WebSocket; // eslint-disable-line no-undef

WS.prototype.doOpen = function() {
    if (!this.check()) {
        // let probe timeout
        return;
    }

    var uri = this.uri();
    var protocols = this.protocols;
    var opts = {};

    if(!this.isReactNative){
        opts.agent = this.agent;
        opts.perMessageDeflate = this.perMessageDeflate;

        // SSL options for Node.js client
        opts.pfx = this.pfx;
        opts.key = this.key;
        opts.passphrase = this.passphrase;
        opts.cert = this.cert;
        opts.ca = this.ca;
        opts.ciphers = this.ciphers;
        opts.rejectUnauthorized = this.rejectUnauthorized;
    }


    if (this.extraHeaders) {
        opts.headers = this.extraHeaders;
    }
    if (this.localAddress) {
        opts.localAddress = this.localAddress;
    }

    try {
        this.ws =
            this.usingBrowserWebSocket && !this.isReactNative
                ? protocols
                ? new WebSocketImpl(uri, protocols)
                : new WebSocketImpl(uri)
                : new WebSocketImpl(uri, protocols, opts);
    } catch (err) {
        return this.emit('error', err);
    }

    if (this.ws.binaryType === undefined) {
        this.supportsBinary = false;
    }

    if (this.ws.supports && this.ws.supports.binary) {
        this.supportsBinary = true;
        this.ws.binaryType = 'nodebuffer';
    } else {
        this.ws.binaryType = 'arraybuffer';
    }

    this.addEventListeners();
};

SaveYourTime · 2020-04-21T05:08:17Z

const _io = ioClient.connect(socketurl, { forceNode: true });
It's work

It works with me, Thanks!

"socket.io-client": "^2.3.0"

const socket = io(host, { forceNode: true });

dommangetnicolas · 2020-04-24T06:42:42Z

const _io = ioClient.connect(socketurl, { forceNode: true });
It's work

It works with me, Thanks!

"socket.io-client": "^2.3.0"
const socket = io(host, { forceNode: true });

It worked for me too! Big thanks

s-vigneshwaran · 2020-04-28T08:24:42Z

You can simply add some headers and it works!
socket = io.connect('SOCKET_URL_HERE', { jsonp: false, agent: '-', pfx: '-', cert: '-', ca: '-', ciphers: '-', rejectUnauthorized: '-', perMessageDeflate: '-' });

AlexandruCalinica · 2020-05-14T14:14:11Z

const _io = ioClient.connect(socketurl, { forceNode: true });

This resolves the warning but makes my socket connection really really slow(timeout actually), so its unusable for me.

lrondanini · 2020-05-20T17:48:53Z

const _io = ioClient.connect(socketurl, { forceNode: true });

This resolves the warning but makes my socket connection really really slow(timeout actually), so its unusable for me.

same here: connection timeout!

darrenkeen · 2020-05-21T09:26:20Z

I got rid of froceNode and downgraded to 2.1.0 and it worked fine. I also had the issue where I was using localhost and not the IP to my emulator device.

isthaison · 2020-05-25T01:19:23Z

The same @SaveYourTime , I'm using "socket.io-client": "^2.3.0"
refer here https://socket.io/docs/client-api/.
I why add forceNode option

BassemN · 2020-06-23T22:41:36Z

This issue should be fixed on engine.io-client v3.4.3 so all you need to do is to delete the yarn.lock file and the node_modules directory then run yarn install

ref socketio/engine.io-client@2f5c948

peterboyer · 2020-10-01T10:50:04Z

@BassemN Perhaps instead of deleting your yarn.lock file, you could use yarn upgrade-interactive to bump the version safely?

It seems a bit counter-intuitive to the idea of a "lock" file if you completely destroy it every time you want to upgrade your packages. 😅

darrachequesne · 2020-10-01T10:56:40Z

It should be fixed by socketio/engine.io-client@e5bc106 (included in engine.io-client@3.4.3 and socket.io-client@2.3.0).

Regarding the forceNode option, it seems React Native actually supports WebSocket (ref), so forceNode: true should not be needed. Isn't that the case?

umitayt · 2022-04-11T09:08:39Z

Proxying WebSockets is working for me.
I am using node HTTP-proxy to allow 'ws' on the local machine, on a remote server configured Nginx proxy.

Server Side:
const io = require("socket.io")(server.listener, {
log: true,
pingInterval: 60000,
pingTimeout: 600000,
cors: {
origin: "http://localhost:3000",
methods: ["GET", "POST"]
}
});
const proxy = HttpProxy.createProxyServer({ ws: true });
io.on("upgrade", function(req, socket, head) {
proxy.ws(req, socket, head);
});

Front Side:
import {Manager} from "socket.io-client";
socketInstance = new Manager('ws://localhost:1342/',
{ transports: ["websocket"] ,
protocols:["http"],
port:1342,
auth:{ token: xxxxxx}
});

mnicole mentioned this issue May 23, 2019

Socket io, fixes and cleanup emote-chat/client#15

Merged

JamesMahy added a commit to SoSa-Community/app-oldnew that referenced this issue Feb 2, 2020

Issue: socketio/socket.io-client#1290

e1b4222

soullivaneuh mentioned this issue Mar 8, 2020

React Native + Expo: Unrecognized WebSocket connection option(s) feathersjs/feathers#1855

Closed

sixclones mentioned this issue May 13, 2020

Cannot connect to feathers server through socket with React Native get timeout feathersjs/feathers#1953

Closed

darrachequesne added this to the 2.3.0 milestone Oct 1, 2020

darrachequesne added the bug Something isn't working label Oct 1, 2020

vikasg603 mentioned this issue Nov 9, 2020

Unrecognized WebSocket connection option(s) localAddress. Did you mean to put these under headers #1395

Closed

1 task

darrachequesne closed this as completed Nov 9, 2020

Unrecognized WebSocket connection option(s) agent, perMessageDeflate, pfx, key, passphrase, cert, ca, ciphers, rejectUnauthorized. Did you mean to put these under headers? #1290

Unrecognized WebSocket connection option(s) agent, perMessageDeflate, pfx, key, passphrase, cert, ca, ciphers, rejectUnauthorized. Did you mean to put these under headers? #1290

Comments

JuAlexandre commented Apr 15, 2019

You want to:

Current behaviour

Steps to reproduce (if the current behaviour is a bug)

bogoslavskiy commented Apr 21, 2019

Luomusha commented Apr 23, 2019

evaleirasclapps commented May 6, 2019

nsafai commented May 7, 2019 • edited

hbouhadji commented May 9, 2019

wx962464 commented May 22, 2019

maxgfr commented Jul 1, 2019

vietmobilefolk commented Jul 4, 2019

marcinczenko commented Jul 8, 2019

samuelgoldenbaum commented Aug 8, 2019

litsdm commented Aug 13, 2019 • edited

FrederickEngelhardt commented Aug 15, 2019 • edited

AminHwadria commented Sep 4, 2019 • edited

Andrielson commented Oct 4, 2019

ghost commented Oct 18, 2019 • edited by ghost

emclab commented Oct 18, 2019

ashadnasim52 commented Oct 22, 2019

jhoanborges commented Oct 29, 2019

canaanites commented Oct 29, 2019

jeanlambert17 commented Nov 14, 2019 • edited

jeanlambert17 commented Nov 14, 2019

peterboyer commented Nov 20, 2019

jzambrano12 commented Jan 27, 2020 • edited

You want to:

Current behaviour

Steps to reproduce (if the current behaviour is a bug)

prettydev commented Feb 1, 2020

JamesMahy commented Feb 2, 2020 • edited

ioness commented Feb 26, 2020

soullivaneuh commented Mar 8, 2020

soullivaneuh commented Mar 8, 2020

schumannd commented Mar 11, 2020 • edited

peterboyer commented Mar 11, 2020

MrCheater commented Mar 12, 2020

BassemN commented Mar 12, 2020

rburson commented Mar 15, 2020

rasoul707 commented Mar 18, 2020

isthaison commented Mar 31, 2020

BassemN commented Mar 31, 2020

marcorm commented Apr 5, 2020

dayaki commented Apr 13, 2020

BassemN commented Apr 13, 2020

SaveYourTime commented Apr 21, 2020 • edited

dommangetnicolas commented Apr 24, 2020

s-vigneshwaran commented Apr 28, 2020

AlexandruCalinica commented May 14, 2020

lrondanini commented May 20, 2020

darrenkeen commented May 21, 2020

isthaison commented May 25, 2020

BassemN commented Jun 23, 2020 • edited

peterboyer commented Oct 1, 2020

darrachequesne commented Oct 1, 2020

umitayt commented Apr 11, 2022

Unrecognized WebSocket connection option(s) `agent`, `perMessageDeflate`, `pfx`, `key`, `passphrase`, `cert`, `ca`, `ciphers`, `rejectUnauthorized`. Did you mean to put these under `headers`? #1290

Unrecognized WebSocket connection option(s) `agent`, `perMessageDeflate`, `pfx`, `key`, `passphrase`, `cert`, `ca`, `ciphers`, `rejectUnauthorized`. Did you mean to put these under `headers`? #1290

nsafai commented May 7, 2019 •

edited

litsdm commented Aug 13, 2019 •

edited

FrederickEngelhardt commented Aug 15, 2019 •

edited

AminHwadria commented Sep 4, 2019 •

edited

ghost commented Oct 18, 2019 •

edited by ghost

jeanlambert17 commented Nov 14, 2019 •

edited

jzambrano12 commented Jan 27, 2020 •

edited

JamesMahy commented Feb 2, 2020 •

edited

schumannd commented Mar 11, 2020 •

edited

SaveYourTime commented Apr 21, 2020 •

edited

BassemN commented Jun 23, 2020 •

edited