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

Push: TypeError: Cannot read property 'device' of undefined #1526

Closed
markuswinkler opened this issue Apr 17, 2016 · 5 comments · Fixed by #1543
Closed

Push: TypeError: Cannot read property 'device' of undefined #1526

markuswinkler opened this issue Apr 17, 2016 · 5 comments · Fixed by #1543

Comments

@markuswinkler
Copy link

I get this error message every time I send a push message (via the onesignal adapter) on the console.
parse-server 2.2.7
Target is iOS only and to a (user) channel.
Could that be related to issue #1245?

error: error while sending push TypeError: Cannot read property 'device' of undefined
    at /Users/markus/ParseServer/node_modules/parse-server/lib/pushStatusHandler.js:81:20
    at Array.reduce (native)
    at Object.complete (/Users/markus/ParseServer/node_modules/parse-server/lib/pushStatusHandler.js:79:15)
    at /Users/markus/ParseServer/node_modules/parse-server/lib/Controllers/PushController.js:130:27
    at run (/Users/markus/ParseServer/node_modules/babel-polyfill/node_modules/core-js/modules/es6.promise.js:89:22)
    at /Users/markus/ParseServer/node_modules/babel-polyfill/node_modules/core-js/modules/es6.promise.js:102:28
    at flush (/Users/markus/ParseServer/node_modules/babel-polyfill/node_modules/core-js/modules/_microtask.js:14:5)
    at _combinedTickCallback (node.js:376:9)
    at process._tickDomainCallback (node.js:431:11)
@flovilmart
Copy link
Contributor

Seems that the one signal adapter don't implement the push status correctly. I'll make a fix over there.

flovilmart added a commit that referenced this issue Apr 19, 2016
Fixes error thrown by #1526
@flovilmart
Copy link
Contributor

On a second thought, I don't think we can get a proper status from one signal, the fix will just let it go through.

@markuswinkler
Copy link
Author

ok.
the messages themselves get sent, there is just the error message afterwards.

drew-gross pushed a commit that referenced this issue Apr 19, 2016
@fasa23
Copy link

fasa23 commented Apr 25, 2016

Make sure you are logged in to your server as root user, i had the same issue and then I realized I was logged in as a user I created with root privileges.

@coolnalu
Copy link

coolnalu commented May 3, 2016

is there a temporal fix?

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

Successfully merging a pull request may close this issue.

4 participants