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

Uncaught TypeError: Cannot read property 'id' of null #125

Open
leedongwei opened this issue Jul 3, 2018 · 1 comment
Open

Uncaught TypeError: Cannot read property 'id' of null #125

leedongwei opened this issue Jul 3, 2018 · 1 comment
Labels

Comments

@leedongwei
Copy link

Steps to reproduce

This is a weird issue to reproduce as it appears on staging/production build only. I can't tell if it's Webpack that's creating the problem, or it appears due to latency between client/server.

Stacktrace points to this line of code that's causing issues. It may be a similar issue to #111.

To cause the error, I create then delete a document. I am working around it by setting listStrategy: always. Sorry for the scant report, I'll update when I have more info.

Expected behavior

No errors

Actual behavior

Uncaught TypeError: Cannot read property 'id' of null
    at feathers-reactive.js:498
    at Array.filter (<anonymous>)
    at a (feathers-reactive.js:497)
    at feathers-reactive.js:505
    at t.accumulator (feathers-reactive.js:538)
    at t._tryNext (feathers-reactive.js:10214)
    at t._next (feathers-reactive.js:10207)
    at t.next (feathers-reactive.js:3386)
    at t.notifyNext (feathers-reactive.js:8913)
    at t._next (feathers-reactive.js:2613)
    at t.next (feathers-reactive.js:3386)
    at t._next (feathers-reactive.js:8635)
    at t.next (feathers-reactive.js:3386)
    at t._next (feathers-reactive.js:8635)
    at t.next (feathers-reactive.js:3386)
    at r.a (feathers-reactive.js:4689)
    at r.emit (index.js:133)
    at r.onevent (socket.js:275)
    at r.onpacket (socket.js:237)
    at r.<anonymous> (index.js:21)
    at r.emit (index.js:133)
    at r.ondecoded (manager.js:345)
    at s.<anonymous> (index.js:21)
    at s.r.emit (index.js:133)
    at s.add (index.js:251)
    at r.ondata (manager.js:335)
    at r.<anonymous> (index.js:21)
    at r.emit (index.js:133)
    at r.onPacket (socket.js:456)
    at r.<anonymous> (socket.js:273)
    at r.emit (index.js:133)
    at r.onPacket (transport.js:145)
    at r.onData (transport.js:137)
    at WebSocket.ws.onmessage (websocket.js:147)

System configuration

"@feathersjs/client": "3.5.3",
"feathers-reactive": "0.7.1",
"feathers-redux": "2.1.0",
"react": "16.2.0",
"redux": "3.7.2",

Tell us about the applicable parts of your setup.

@dottodot
Copy link

dottodot commented Jul 9, 2018

The issue I reported in #111 has actually come back for me so I've don't think it's been completely fixed. It's a bit confusing as it's not happening all the time. For example I have 2 places where I'm creating documents using the same code the only difference being the data submitted and the service being called.

@daffl daffl added the bug label Aug 25, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants