Skip to content

value.resolvedPage.__path always undefined #13

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

Closed
ScottAtRedHawk opened this issue Oct 9, 2019 · 3 comments
Closed

value.resolvedPage.__path always undefined #13

ScottAtRedHawk opened this issue Oct 9, 2019 · 3 comments

Comments

@ScottAtRedHawk
Copy link

Hi,
In /components/Navigator.js line 46 value.resolvedPage.__path is always undefined, so the call to _updatePath() always passes the default route. The routing is working as far as screens go, but when I call this.$navigator.route in a component, it is always the default route object and not the current route that the app has navigated to.

@rigor789
Copy link
Member

rigor789 commented Oct 9, 2019

@ScottAtRedHawk can you include a sample repository where this is not working? I'm using this pacakage with nativescript 6.x and it's working (this.$navigator.route works too).

@ScottAtRedHawk
Copy link
Author

I'm not sure what I'm doing but it seems to work intermittently. I'm going to close this because I don't think it's an issue with the package, but rather my code. Thanks!

@rigor789
Copy link
Member

@ScottAtRedHawk if you need help debugging, share your issue on Slack, someone might be able to spot the issue!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants