Invalid parameter for query: audience_limit

[sakhunzai]

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

local docker instance, with node:8.11

"dependencies": {
    "@parse/fs-files-adapter": "^1.0.1",
    "@parse/push-adapter": "^3.0.0",
    "@parse/s3-files-adapter": "^1.2.1",
    "express": "~4.16.x",
    "kerberos": "~1.1.x",
    "mailgun-js": "~0.22.x",
    "parse": "~2.1.0",
    "parse-dashboard": "^1.2.0",
    "parse-server": "~3.1.3",
    "parse-server-mailgun": "~2.4.x",
    "remove": "^0.1.5"
  },

Steps to reproduce

open in browser: http://localhost:1337/dashboard/apps/myapp/push/audiences

Logs/Trace

error: Invalid parameter for query: audience_limit message=Invalid parameter for query: audience_limit, stack=Error: Invalid parameter for query: audience_limit
    at Function.optionsFromBody (/parse/node_modules/parse-server/lib/Routers/ClassesRouter.js:127:15)
    at AudiencesRouter.handleFind (/parse/node_modules/parse-server/lib/Routers/AudiencesRouter.js:26:44)
    at _ClassesRouter.default.mountRoutes.route.req (/parse/node_modules/parse-server/lib/Routers/AudiencesRouter.js:47:19)
    at route.handlers.reduce.promise.then (/parse/node_modules/parse-server/lib/PromiseRouter.js:85:20)
    at <anonymous>
    at process._tickDomainCallback (internal/process/next_tick.js:228:7), code=102

I see the dashboard has public/bundles/dashboard.bundle.js with "push_audiences?audience_limit", which is invalid w.r.t parse-server ~3.1.3. Which mean there is no dashboard release compatible with latest parse-server release version. I do not see any suitable solution except downgrade the parse-server, which I do not like. I see there is already a fix commit #813 , is it possible to release a bug fix any soon , thanks.

[stale]

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.