Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IncomingStream becomes inactive #10

Open
ghost opened this issue Feb 17, 2018 · 1 comment
Open

IncomingStream becomes inactive #10

ghost opened this issue Feb 17, 2018 · 1 comment

Comments

@ghost
Copy link

ghost commented Feb 17, 2018

Hi, I recently started using your module, and when I created an IncomingStream to detect messages to a user, everything works fine for a while. But after a few minutes of inactivity the on('message') events appear to stop firing.

Is there something I need to do to keep the connection fresh, or to keep the message events firing?

Thanks!

@not-so-smart
Copy link

This is because the groupme package doesn't handle websocket connections correctly. As mentioned in the API docs, the client token must be refreshed every (x) interval. The interval has changed since the documentation was written, but a proper implementation would handle this correctly regardless of the interval.

Check out the node-groupme package in my repository for an updated library that properly handles the GroupMe websocket interface.

https://github.com/not-so-smart/node-groupme

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant