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

Access to Push > Create an audience returns 404 #2626

Open
4 tasks done
pdsolutions opened this issue Nov 1, 2024 · 1 comment
Open
4 tasks done

Access to Push > Create an audience returns 404 #2626

pdsolutions opened this issue Nov 1, 2024 · 1 comment
Labels
type:bug Impaired feature or lacking behavior that is likely assumed

Comments

@pdsolutions
Copy link

pdsolutions commented Nov 1, 2024

New Issue Checklist

Issue Description

Unable to Create an audience in Push
Please note that it fails on parse-dashboard": 6.0.0 on dokku and [email protected] on local fresh installation.

Steps to reproduce

In order to reproduce please login -> Push -> Create an audience

On parse dashboard 5.3.0 with "parse-server": "^5.6.0" it's working, please see the latest attached image.

UPDATE:
I've installed parse dashboard 5.4.0 on local, configured parse-dashboard-config.json with both apps, one on a parse server 7.3.0 and another on 5.6.0 and it works, so the problem is parse dashboard 6.0.0

Actual Outcome

Blank page, no popup

Expected Outcome

Create an audience popup

Environment

Dokku package.json:

"dependencies": {
"@parse/fs-files-adapter": "^3.0.0",
"@parse/s3-files-adapter": "^3.0.0",
"@parse/simple-mailgun-adapter": "^2.0.0",
"aws-sdk": "^2.1691.0",
"axios": "^1.7.7",
"cookie-parser": "^1.4.7",
"cookie-session": "^2.1.0",
"dotenv": "^16.4.5",
"ejs": "^3.1.10",
"express": "^4.21.1",
"express-ejs-layouts": "^2.5.1",
"i18n": "^0.15.1",
"limax": "^4.1.0",
"mailgen": "^2.0.28",
"mailgun.js": "^10.2.3",
"method-override": "^3.0.0",
"moment": "^2.30.1",
"node-cron": "^3.0.3",
"parse": "^5.3.0",
"parse-dashboard": "^6.0.0",
"parse-server": "^7.3.0",
"parse-server-mailgun-adapter-template": "^1.1.7",
"pm2": "^5.4.2",
"sharp": "^0.33.5",
"stripe": "^17.3.0",
"winston": "^3.15.0"
}
...

Local package.json -> see on https://github.com/parse-community/parse-dashboard/

parse-dashboard-config.json:
{
"apps": [
{
"serverURL": "https://domain/api",
"appId": "myAppId",
"masterKey": "example",
"appName": "example",
"iconName": "",
"primaryBackgroundColor": "#003a87",
"secondaryBackgroundColor": "#0067f0"
}
],
"iconsFolder": "icons"
}

Dashboard

  • Parse Dashboard version: 6.0.0
  • Browser (Safari, Chrome, Firefox, Edge, etc.): Chrome
  • Browser version: 130.0.6723.91 (Build oficial) (arm64)

Server

  • Parse Server version: 7.3.0
  • Operating system: Ubuntu with Dokker 24.0.7
  • Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc): Custom VPS with Dokker 24.0.7

Database

  • System (MongoDB or Postgres): MongoDB
  • Database version: 8.0.1
  • Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc): remote, same server same dokku

Logs

There are no significant logs in the dokku logs <app_name>
Blank page with err in Chrome console:

dashboard.bundle.js:2 TypeError: Cannot read properties of undefined (reading 'undefined')
at Object.m (dashboard.bundle.js:2:933407)
at Gp (dashboard.bundle.js:2:3006032)
at Jo (dashboard.bundle.js:2:1952946)
at Es (dashboard.bundle.js:2:1998904)
at kl (dashboard.bundle.js:2:1991688)
at xl (dashboard.bundle.js:2:1991613)
at fl (dashboard.bundle.js:2:1988646)
at dashboard.bundle.js:2:1940360
at t.unstable_runWithPriority (dashboard.bundle.js:2:2182421)
at Ki (dashboard.bundle.js:2:1940069)

Captura de pantalla 2024-11-01 a las 11 54 06 Captura de pantalla 2024-11-01 a las 11 54 39 Captura de pantalla 2024-11-01 a las 11 55 14 Captura de pantalla 2024-11-01 a las 12 33 06
Copy link

parse-github-assistant bot commented Nov 1, 2024

Thanks for opening this issue!

  • 🚀 You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.

@mtrezza mtrezza added the type:bug Impaired feature or lacking behavior that is likely assumed label Nov 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Impaired feature or lacking behavior that is likely assumed
Projects
None yet
Development

No branches or pull requests

2 participants