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

Switching apps not working #1994

Closed
4 tasks done
404-html opened this issue Jan 12, 2022 · 3 comments · Fixed by #2010
Closed
4 tasks done

Switching apps not working #1994

404-html opened this issue Jan 12, 2022 · 3 comments · Fixed by #2010
Labels
bounty:$20 Bounty applies for fixing this issue (Parse Bounty Program) type:bug Impaired feature or lacking behavior that is likely assumed

Comments

@404-html
Copy link
Member

New Issue Checklist

Issue Description

switching-apps-broken

Steps to reproduce

  1. Go to data browser;
  2. Switch to different app;

Actual Outcome

Data browser performs a refresh but it still shows data from original app.

Expected Outcome

Chosen app should become selected and browser should show data from it.

Environment

Dashboard

  • Parse Dashboard version: 4.0.0-beta.1
  • Browser (Safari, Chrome, Firefox, Edge, etc.): Chrome
  • Browser version: 97.0.4692.71

Server

  • Parse Server version: 4.10.4
  • Operating system: Linux
  • Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc): Google Cloud

Database

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

Logs

Nothing gets logged in browser' dev tools.

@404-html 404-html added the type:bug Impaired feature or lacking behavior that is likely assumed label Jan 12, 2022
@mtrezza
Copy link
Member

mtrezza commented Jan 12, 2022

Could this be related to #1991?

@mtrezza mtrezza added the bounty:$20 Bounty applies for fixing this issue (Parse Bounty Program) label Jan 12, 2022
@mtrezza
Copy link
Member

mtrezza commented Jan 21, 2022

@404-html Could you try to find out the earliest release that introduced the issue, so we can narrow down which commit introduced the issue.

@mtrezza mtrezza mentioned this issue Jan 21, 2022
3 tasks
@404-html
Copy link
Member Author

Later I will try to find exact commit with git bisect but my gut feeling is that the cause is the same like here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bounty:$20 Bounty applies for fixing this issue (Parse Bounty Program) type:bug Impaired feature or lacking behavior that is likely assumed
Projects
None yet
2 participants