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.

Sign up for GitHub

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

Jump to bottom

Transitioning from one engine route to another triggers a Cannot read properties of undefined (reading 'shouldSupersede') #850

Open
axelerate opened this issue Sep 21, 2023 · 0 comments
Open

Transitioning from one engine route to another triggers a Cannot read properties of undefined (reading 'shouldSupersede') #850

axelerate opened this issue Sep 21, 2023 · 0 comments

Comments

@axelerate
Copy link

Transitioning from one engine route to another triggers a Cannot read properties of undefined (reading 'shouldSupersede').
This issue happens intermittently and I am not able to reproduce in a sandbox environment.

The issue cannot be reproduced in version v0.8.23 and only surfaces when upgrading to Ember Engines v0.9.0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@axelerate