nativescript-angular: After upgraded to NativeScript 3.2.0 - TypeError: Cannot read property 'reusedRoute' of undefined

From @shabib3 on September 7, 2017 22:16

Did you verify this is a real problem by searching [Stack Overflow]

Yes… I found this but this didn’t work for me…plus it happens with the upgrading for the new version which not happened before

Tell us about the problem

After I upgraded the NativeScript to the new 3.2.0 version… It throw me the following error right after navigate with clearHistory: true property: TypeError: Cannot read property ‘reusedRoute’ of undefined

JS: ERROR Error: Uncaught (in promise): TypeError: Cannot read property 'reusedRoute' of undefined
JS: TypeError: Cannot read property 'reusedRoute' of undefined
JS:     at PageRouterOutlet.activateOnGoBack (file:///data/data/com.staccato.app/files/app/tns_modules/nativescript-angular/router/page-router-outlet.js:177:18)
JS:     at PageRouterOutlet.activateWith (file:///data/data/com.staccato.app/files/app/tns_modules/nativescript-angular/router/page-router-outlet.js:136:18)
JS:     at ActivateRoutes.placeComponentIntoOutlet (file:///data/data/com.staccato.app/files/app/tns_modules/@angular/router/bundles/router.umd.js:4526:16)
JS:     at ActivateRoutes.activateRoutes (file:///data/data/com.staccato.app/files/app/tns_modules/@angular/router/bundles/router.umd.js:4507:26)
JS:     at file:///data/data/com.staccato.app/files/app/tns_modules/@angular/router/bundles/router.umd.js:4443:58
JS:     at Array.forEach (native)
JS:     at ActivateRoutes.activateChildRoutes (file:///data/data/com.staccato.app/files/app/tns_modules/@angular/router/bundles/router.umd.js:4443:29)
JS:     at ActivateRoutes.activate (file:///data/data/com.staccato.app/files/app/tns_modules/@angular/router/bundles/router.umd.js:4417:14)
JS:     at file:///data/data/com.staccato.app/files/app/tns_modules/@angular/router/bundles/router.umd.js:4034:22
JS:     at SafeSubscriber._next (file:///data/data/com.staccato.app/files/app/tns_modules/rxjs/Observable.js:110:21)
JS:     at SafeSubscriber.__tryOrSetError (file:///data/data/com.staccato.app/files/app/tns_modules/rxjs/Subscriber.js:247:16)
JS:     at SafeSubscriber.next (file:///data/data/com.staccato.app/files/app/tns_modules/rxjs/Subscriber.js:187:27)
JS:     at Subscriber._next (file:///data/data/com.staccato.app/files/app/tns_modules/rxjs/Subscriber.js:125:26)
JS:     at Subscriber.next (file:///data/data/com.staccato.app/files/app/tns_modules/rxjs/Subscriber.js:89:18)
JS:     at MapSubscriber._next (file:///data/data/com.staccato.app/files/app/tns_modules/rxjs/operator/map.js:83:26)

Which platform(s) does your issue occur on?

Android

Please provide the following version numbers that your issue occurs with:

CLI: 3.2.0
Cross-platform modules: 3.2.0

Copied from original issue: NativeScript/NativeScript#4813

About this issue

Original URL
State: closed
Created 7 years ago
Comments: 22 (3 by maintainers)

Most upvoted comments

Update: We are actively working on the issue. It is actually an issue in the tns-core-modules so the fix will be done there.

+11

vakrilov on Oct 12, 2017

Same here, it happens with the case of @shabib3 :

page2 navigate to page3 with the following metadata { clearHistory: true }

It does that for any page I want to clear history of.

echap on Sep 28, 2017

I know it does not help, but this bug is avoiding releases for complex apps such as ours for two reasons :

We really can’t let people get back on some activities (forms submissions…)
We also need to clear history to limit the memory footprint in our app, and this kind of routing is actually destroying components which launches garbage collection ( we basically taken advantage of this feature after some issues with memory leaks that was crashing our app).

I just wanted to point this out because I don’t think we’re the only ones relying on your awesome nativescript angular, and we’re stuck with our release roadmap ! 😃

echap on Oct 4, 2017

+1, this is a big issue in our app at the moment.

micflan on Sep 20, 2017

Yup! The issue seems to be resolved with 3.3! Thank @hshristov for that 😃

vakrilov on Oct 31, 2017

@NickIliev How can we proceed investigate this issue?

Thanks! 😃

bzaruk on Sep 22, 2017

@micflan For sure, it is.

I had to postpone some updates in my apps because of that.

Hope for a solution any time soon. Regards

smarza on Sep 20, 2017