-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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 Dashboard cannot open since 2.6.0 #4302
Comments
please provide the logs when running with VERBOSE=1 |
Can you also provide the failing requests/responses from the browser/parse-dashboard ? |
This is running 2.6.2 Here is the screenshot in chrome.
|
I then checked AudiencesRouter line 56. It crashed at the JSON.parse because the item.query is already an object. `
` So I deleted all the audience documents from mongodb. They are just previous saved push audience queries. Then there is no errors any more but the push page still not loading. Here is the new screenshot screenshot It hangs at this loading stage. |
Same issue here, any update? Using: "parse": "1.10.2",
"parse-dashboard": "1.1.2",
"parse-server": "2.6.5", btw if I go back to the old version of parse-dashboard: Using: "parse": "1.10.2",
"parse-dashboard": "1.1.0",
"parse-server": "2.6.5", The error is still shown but the Push section works. |
Please see #811 in parse-dashboard and the merged PR. This will not be available until the next release is published by the way. In the meantime try configuring your push localizations and see if that doesn't fix it. |
Hey @montymxb thanks for the heads-up; do you know how can I test it? And I've tried to do a If the only way to "have that fix" is for @flovilmart to do a new release, can I ask you if there is any way I can help in getting to a point that a release for |
@kelset Until a new release is published you have a couple of options.
If you're up for it you can also try building the dashboard yourself. But I imagine you're getting it from npm and you would probably like to keep it that way. |
As @montymxb pointed out, the dashboard not opening was an issue with parse-dashboard, which was patched in 1.2.0. However, using both the latest parse-dashboard (1.2.0) and parse-server (2.7.4), opening the push page is still causing a lot of server error logs similar to what @tjlian616 mentioned. Are these of concern?
Pushes are sending properly, and the dashboard now opens, but the Potentially also of note: I do not have any Audiences at all. I saw in the other repo the error with the dashboard not opening the push page was old Audience objects not having a pushLocale value or something. I do not have any audiences, so it shouldn't be missing data from those audiences. Maybe it's the lack of audiences entirely? Is this something to report on the Parse-Dashboard repo, or is it a Parse-Server issue? |
@JacobJT Check the You may not see existing audiences in the dashboard because the audience entries cannot be displayed due to, well, the error you are describing. |
@mtrezza Ahh, I do see a single _Audience value dating back to 2016, going by the date this was after we migrated to our own database, though I don't think we had yet left Parse.com. Is there a way to delete this via the mLab dashboard? or am I going to have to use the mongo cli for this? |
@JacobJT To delete it via the mLab dashboard go to |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Issue Description
Ever since upgrading to 2.6.0, I'm not able to open/view the Push section in parse dashboard. The page keeps on loading in 2.6.0 and becomes all white in 2.6.2
Steps to reproduce
Run parse server and parse dashboard on localhost. Click on Core and you can see all classes. Click on Push and it hangs there.
I even went to dabase and manually deleted all the Audience records but it didn't help.
Logs/Trace
this is on 2.6.0
parse-server-example running on port 1337.
error: Error generating response. ParseError { code: 1, message: 'bad key in untransform: _last_used' } code=1, message=bad key in untransform: _last_used
error: bad key in untransform: _last_used code=1, message=bad key in untransform: _last_used
this is on 2.6.1
error: Error generating response. SyntaxError: Unexpected token o in JSON at position 1
at Object.parse (native)
at /Users/anli/Documents/workspace_apollo/apolloParseServer/node_modules/parse-server/lib/Routers/AudiencesRouter.js:57:29
at Array.forEach (native)
at /Users/anli/Documents/workspace_apollo/apolloParseServer/node_modules/parse-server/lib/Routers/AudiencesRouter.js:56:26
at process._tickDomainCallback (internal/process/next_tick.js:135:7)
error: Uncaught internal server error. SyntaxError: Unexpected token o in JSON at position 1
at Object.parse (native)
at /Users/anli/Documents/workspace_apollo/apolloParseServer/node_modules/parse-server/lib/Routers/AudiencesRouter.js:57:29
at Array.forEach (native)
at /Users/anli/Documents/workspace_apollo/apolloParseServer/node_modules/parse-server/lib/Routers/AudiencesRouter.js:56:26
at process._tickDomainCallback (internal/process/next_tick.js:135:7) SyntaxError: Unexpected token o in JSON at position 1
at Object.parse (native)
at /Users/anli/Documents/workspace_apollo/apolloParseServer/node_modules/parse-server/lib/Routers/AudiencesRouter.js:57:29
at Array.forEach (native)
at /Users/anli/Documents/workspace_apollo/apolloParseServer/node_modules/parse-server/lib/Routers/AudiencesRouter.js:56:26
at process._tickDomainCallback (internal/process/next_tick.js:135:7)
SyntaxError: Unexpected token o in JSON at position 1
at Object.parse (native)
at /Users/anli/Documents/workspace_apollo/apolloParseServer/node_modules/parse-server/lib/Routers/AudiencesRouter.js:57:29
at Array.forEach (native)
at /Users/anli/Documents/workspace_apollo/apolloParseServer/node_modules/parse-server/lib/Routers/AudiencesRouter.js:56:26
at process._tickDomainCallback (internal/process/next_tick.js:135:7)
Environment Setup
Server
Database
The text was updated successfully, but these errors were encountered: