If I navigate to non-nested route (route that does not have another page-router-outlet) it works fine.Įdit: This is when navigating from page-router-outlet to nested page-router-outlet and than going back to the first page-router-outlet. JS: Error: Uncaught (in promise): TypeError: Cannot read property 'urlPath' of null JS: Unhandled Promise rejection: Cannot read property 'urlPath' of null Zone: angular Task: Promise.then Value: TypeError: Cannot read property 'urlPath' of null JS: at ZoneDelegate.invoke (/data/data/mk.vertex.instantaxipartner/files/app/tns_modules/zone.js/dist/zone-node.js:281:29) JS: at ZoneTask.invoke (/data/data/mk.vertex.instantaxipartner/files/app/tns_modules/zone.js/dist/zone-node.js:384:22) JS: at drainMicroTaskQueue (/data/data/mk.vertex.instantaxipartner/files/app/tns_modules/zone.js/dist/zone-node.js:432:36) JS: at nTask (/data/data/mk.vertex.instantaxipartner/files/app/tns_modules/zone.js/dist/zone-node.js:214:48) JS: at .fork.onInvokeTask at ZoneDelegate.invokeTask (/data/data/mk.vertex.instantaxipartner/files/app/tns_modules/zone.js/dist/zone-node.js:313:43) JS: at ZoneDelegate.invokeTask (/data/data/mk.vertex.instantaxipartner/files/app/tns_modules/zone.js/dist/zone-node.js:314:38) JS: at /data/data/mk.vertex.instantaxipartner/files/app/tns_modules/zone.js/dist/zone-node.js:529:18 JS: at resolvePromise (/data/data/mk.vertex.instantaxipartner/files/app/tns_modules/zone.js/dist/zone-node.js:481:18) JS: at resolvePromise (/data/data/mk.vertex.instantaxipartner/files/app/tns_modules/zone.js/dist/zone-node.js:496:32) Which platform(s) does your issue occur on?īoth Please provide the following version numbers that your issue occurs with:Ĭopied from original issue: NativeScript/NativeScript#2162Įrror: Uncaught (in promise): TypeError: Cannot read property 'urlPath' of null But Having tabs/view be able to be easily loadable via navigation would improve things, with allowing buttons to remain on bottom but page changes. This might be impossible with the current design. Ability to have TabView/dedicated View (new component required) navigation.In ability to add/modify to the history stack, I might want to insert a "Back" page or maybe even completely rewrite the history stack.I may not know that page needs to be cleared from the history until they do something on it. If I am on a page and I want to navigate off this page and forget it I should be able to delete it from the history stack so that it is like the page was never was originally set with BSV. backStackVisible is NOT the solution to this, as BSV affects the next page being loaded. Inability to delete a page from the history stack This needs to be able to happen after loading a page, then I can clear it from the history.Inability to reload the current page without affecting history, see: Expose the native view form the ListViewComponent #243, NativeScript usage of the new HttpClient - causes error? #1087.#583, Datepicker ngModel not working only on IOS #618 Inability to cancel a navigate (both forward and back) request via the onNavigatingFrom/onNavigatingTo event handlers see Value accessors using static selectors now.□ Tell us about the problemĬurrent Navigation system has the following issues: requested I do this and I am linking to any existing issues in the issue tracker. Yes, this is a combination post describing several issues with the current routing system. From on 23:41 Did you verify this is a real problem by searching
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |