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

Client Side Timeout #761

Closed
Ryan8765 opened this issue Dec 27, 2017 · 3 comments
Closed

Client Side Timeout #761

Ryan8765 opened this issue Dec 27, 2017 · 3 comments

Comments

@Ryan8765
Copy link

Ryan8765 commented Dec 27, 2017

Either I am missing something very basic - or there seems to be a bug associated with the client build. Details to replicate:

  1. Create a new Feathers application
  2. Create a messages service
  3. Set up the index.html page to match the suggested "Load from CDN" section.
  4. Run the server and try adding a message in Chrome/Edge (haven't tested other browsers). Timeout should be seen. With the following error message:
client.js:66 Uncaught (in promise) Error: Timeout of 5000ms exceeded calling create on messages
    at client.js:66

See linked repository with project setup complete to replicate this issue. I am running this locally (3030) on two separate windows 10 computers.

@daffl
Copy link
Member

daffl commented Dec 27, 2017

Your server side application has been created with an old (v2) version of the CLI but you are loading @feathersjs/feathers@^3.0.0 in the browser which uses a Socket.io message format that is not supported by a v2 server.

feathers --version on the command line should show 3.3.0 or later. You can either follow the migration guide to upgrade or install the latest @feathersjs/cli and regenerate the application.

@Ryan8765
Copy link
Author

Worked perfect, thanks!

@lock
Copy link

lock bot commented Feb 7, 2019

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue with a link to this issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Feb 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants