Parse-dashboard: Can't open Push tab

[ChrDel]

Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Dashboard!

• [X] You're running version >=1.0.23 of Parse Dashboard.

• [X] You're running version >=2.3.2 of Parse Server.

• [X] You've searched through existing issues. Chances are that your issue has been reported or resolved before.

Environment Setup

PARSE DASHBOARD 1.1.2
PARSE SERVER 2.6.5

Steps to reproduce

Open Parse Dashboard, click on PUSH in the left menu on the bottom.
Nothing seems to happen.
When opening developer tools, in the console there is an error. This error happens when the push menu on the left is clicked.

Logs/Trace

Note: If you get a browser JS error please run npm run dev. This will provide source maps and a much more useful stack trace.

dashboard.bundle.js:47 Uncaught TypeError: Cannot read property 'filter' of undefined
at t.value (dashboard.bundle.js:47)
at d.performInitialMount (dashboard.bundle.js:32)
at d.mountComponent (dashboard.bundle.js:32)
at Object.mountComponent (dashboard.bundle.js:10)
at d.performInitialMount (dashboard.bundle.js:32)
at d.mountComponent (dashboard.bundle.js:32)
at Object.mountComponent (dashboard.bundle.js:10)
at d.performInitialMount (dashboard.bundle.js:32)
at d.mountComponent (dashboard.bundle.js:32)
at Object.mountComponent (dashboard.bundle.js:10)
value @ dashboard.bundle.js:47
performInitialMount @ dashboard.bundle.js:32
mountComponent @ dashboard.bundle.js:32
mountComponent @ dashboard.bundle.js:10
performInitialMount @ dashboard.bundle.js:32
mountComponent @ dashboard.bundle.js:32
mountComponent @ dashboard.bundle.js:10
performInitialMount @ dashboard.bundle.js:32
mountComponent @ dashboard.bundle.js:32
mountComponent @ dashboard.bundle.js:10
updateChildren @ dashboard.bundle.js:32
_reconcilerUpdateChildren @ dashboard.bundle.js:33
_updateChildren @ dashboard.bundle.js:33
updateChildren @ dashboard.bundle.js:33
_updateDOMChildren @ dashboard.bundle.js:33
updateComponent @ dashboard.bundle.js:33
receiveComponent @ dashboard.bundle.js:33
receiveComponent @ dashboard.bundle.js:10
_updateRenderedComponent @ dashboard.bundle.js:32
_performComponentUpdate @ dashboard.bundle.js:32
updateComponent @ dashboard.bundle.js:32
receiveComponent @ dashboard.bundle.js:32
receiveComponent @ dashboard.bundle.js:10
_updateRenderedComponent @ dashboard.bundle.js:32
_performComponentUpdate @ dashboard.bundle.js:32
updateComponent @ dashboard.bundle.js:32
receiveComponent @ dashboard.bundle.js:32
receiveComponent @ dashboard.bundle.js:10
_updateRenderedComponent @ dashboard.bundle.js:32
_performComponentUpdate @ dashboard.bundle.js:32
updateComponent @ dashboard.bundle.js:32
receiveComponent @ dashboard.bundle.js:32
receiveComponent @ dashboard.bundle.js:10
_updateRenderedComponent @ dashboard.bundle.js:32
_performComponentUpdate @ dashboard.bundle.js:32
updateComponent @ dashboard.bundle.js:32
performUpdateIfNecessary @ dashboard.bundle.js:32
performUpdateIfNecessary @ dashboard.bundle.js:10
s @ dashboard.bundle.js:7
perform @ dashboard.bundle.js:12
perform @ dashboard.bundle.js:12
perform @ dashboard.bundle.js:7
S @ dashboard.bundle.js:7
closeAll @ dashboard.bundle.js:12
perform @ dashboard.bundle.js:12
batchedUpdates @ dashboard.bundle.js:33
o @ dashboard.bundle.js:7
dispatchEvent @ dashboard.bundle.js:33

[playvici]

Same issue. Help!

[playvici]

Update - looks like going directly to /push/activity/all and /push/audiences works, just not /push/new. Thoughts?

[playvici]

Also - getting random error:

2017-11-15T19:48:19.769Z - Invalid parameter for query: audience_limit
2017-11-15T19:48:19.765Z - Error generating response. ParseError {
code: 102,
message: 'Invalid parameter for query: audience_limit' }

Thoughts?

[montymxb]

@Pikorua @nextbigidea can confirm that this is happening exclusively on 1.1.2, 1.1.0 is unaffected. There we some recent dependency updates, something in there must have broken this :/. I'll let you know when I find out what's going on here.

[montymxb]

The issue has to do with the newly added localized push feature. Looks like there isn't a check for when it's not present. I've opened up a PR to patch this, but in the meantime you can add an empty array of localizations to fix it.

{
  "apps": [{
    "serverURL": "http://localhost:1337/parse",
    "appId": "app-id-here",
    "masterKey": "master-key-here",
    "appName": "app-name-here",
    "supportedPushLocales": []
  }],
}

[ChrDel]

Ah! Yes, that definitely helped! Thanks heaps @montymxb :D
Side question, should I open another "issue", it seems that this latest version keeps login me out all the time... It was not doing that before...
Thanks again! You guys rock~

[flovilmart]

There’s a new option for the cookie based sessions, the server will log you out when restarting, is that related?

[ChrDel]

No I'm not restarting the server, i'm logging in then i would click on Push and it sends me back to the login screen or i would refresh the page and it would send me back to the login page too...

[montymxb]

Hmm, @Pikorua I would open up a separate issue so we can track that independently of this.

[Droppix]

Same issue with Parse-Dahboard v1.1.2 and Parse-server 2.6.5

Works with Parse-Dashboard v1.1.2 and Parse-server 2.2.25

[montymxb]

@Droppix if it's related to being unable to see the Push section see the answer above ^.

[Droppix]

@montymxb
Works!

Thanks

[montymxb]

Closing this out as resolved. @Pikorua if you're still having a problem with the repeated logout go ahead and open up another issue so we can follow up there.

[gateway]

Any idea when this could get pushed into a new version.. no pun intended :)

[montymxb]

Soon ideally. @flovilmart do we have anything else that would go with this
or can we just make a patch release?

On Nov 29, 2017 13:54, "Gateway" [e-mail] wrote:

Any idea when this could get pushed into a new version.. no pun intended :)

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/parse-community/parse-dashboard/issues/811#issuecomment-348009261,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AE1d4BPTWyMjYT9X27eJeP6e1hmwTIUQks5s7dKWgaJpZM4Qd6eS
.

[flovilmart]

Let’s check the open PR’s and see whst’s Pending, otherwise, I don’t mind

[montymxb]

@flovilmart could release after #813?

[flovilmart]

Yep, we need a review on this one.

[helloaneeskhan]

just make an empty property in your parse-dashboard-config.json
"supportedPushLocales": []

[yuvrajjsingh0]

Thank you very much! @montymxb . I was stuck on this problem for weeks. Since, I'm new in parse.

[alok-pandit]

I tried this:

{
"apps": [{
"serverURL": "http://localhost:1337/parse",
"appId": "app-id-here",
"masterKey": "master-key-here",
"appName": "app-name-here",
"supportedPushLocales": []
}],
}

However, I am still facing the same error.

[email protected]

[email protected]

I am using nvm ( nvm use --lts on ubunu 16.04).

I have added "supportedPushLocales": [] to the /home/alok/.nvm/versions/node/v8.9.4/lib/node_modules/parse-dashboard/Parse-Dashboard/parse-dashboard-config.json file.

[alok-pandit]

Never Mind. Issue resolved. I was running 'parse-dashboard --appId parsePoC --masterKey * --serverURL "http://localhost:1337/parse" --appName parsePoC' when I should have been running just parse-dashboard.

[amitkh6]

@montymxb Can see that you have provided the solution, however I am unable to follow as to what to do where.... Pls guide, any of the member who have benefited pls guide the steps..

Pls excuse my naivety to developer world
@yuvrajjsingh0
@Droppix