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

Navigation Links Intermittently breaking after implementing Auth0 #7

Closed
jsrj opened this issue Apr 6, 2019 · 3 comments
Closed

Navigation Links Intermittently breaking after implementing Auth0 #7

jsrj opened this issue Apr 6, 2019 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@jsrj
Copy link
Owner

jsrj commented Apr 6, 2019

Describe the bug
When clicking on a link in navigation besides "Log In" or "Log Out" (e.g. "Home" or "Profile"), the first link will redirect correctly, but any others afterward do not respond.

To Reproduce
Steps to reproduce the behavior:

  1. Go to Home page
  2. Click on 'Log In'
  3. Log In
  4. Click on 'Profile'
  5. Click on 'About' or 'Home'
  6. Notice the page does not route but address bar URL will change

Expected behavior
When clicking on any link in the Navbar, regardless of authentication state, the router should navigate to that link or to the authentication page. It should not sit at the same page a user is attempting to navigate away from.

Desktop (please complete the following information):

  • OS: Mac OSX 11
  • Browser: Firefox Developer Edition
  • Version: 67.0b6

Additional context
This bug has only appeared after implementing the Auth0 authentication methods and links into the Navbar, and updating the router accordingly.

@jsrj jsrj self-assigned this Apr 6, 2019
@jsrj jsrj added the bug Something isn't working label Apr 6, 2019
@jsrj
Copy link
Owner Author

jsrj commented Apr 7, 2019

Console is currently displaying the following errors that may be related:

[Vue warn]: Error in nextTick: "TypeError: vm._data is undefined" vue.runtime.esm.js:619
TypeError: "vm._data is undefined"

However, there is nowhere in the code I've yet found where either of these values are being called/invoked/referenced. If this is the cause of the routing issue, it is either a bug within the current Vue.js version installed (very unlikely since a prototype of a similar structure has been running fine on the same version), or something else is triggering this error via cascading failure whose root cause is not being caught by Vue itself.

@jsrj
Copy link
Owner Author

jsrj commented Apr 7, 2019

Disabling the LastAction component, since it was throwing an unnoticed warning regarding a prop type mismatch, appears to have resolved the bug. The footer had been throwing a similar warning as well, but was previously disabled. If these are the root cause, then this should resolve the issue.

Documenting this here for future reference.

@jsrj
Copy link
Owner Author

jsrj commented Apr 7, 2019

Confirmed: changing the prop type from [Object] to Array in both the Footer and LastAction components has resolved the issue.

@jsrj jsrj closed this as completed Apr 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant