NativeScript: Regression: Back button breaks app on clearHistory: true (android)

So seems like if you have this scenario, the back button breaks the App, it can’t navigate back any more, and it just crashes.

Create an app using the new version 1.6.0
Create Page1, Page2 and Page3
Make Page1 you initial page, and add a button to navigate to Page2 like: var nav = { moduleName: "./Page2", backstackVisible: true, clearHistory: true }; frame.topmost().navigate(nav)
In Page2, add another button to navigate to Page3, like: exports.toPage3 = function(){ frame.topmost().navigate("./Page3") }
Once in Page3, try to navigate back using the “Back” button on your device, it just crashes, or you get a blank screen sometimes, I also attached a sample app if you want to use it. sampleapp.zip .

About this issue

Original URL
State: closed
Created 8 years ago
Comments: 23 (8 by maintainers)

Commits related to this issue

Fixes #1569 — committed to NativeScript/NativeScript by atanasovg 8 years ago

Most upvoted comments

System.err: android.content.res.Resources$NotFoundException: Resource ID #0xffffffec
System.err:     at android.content.res.ResourcesImpl.getValue(ResourcesImpl.java:215)
System.err:     at android.content.res.Resources.loadXmlResourceParser(Resources.java:2134)
System.err:     at android.content.res.Resources.getAnimation(Resources.java:1167)
System.err:     at android.animation.AnimatorInflater.loadAnimator(AnimatorInflater.java:125)
System.err:     at android.animation.AnimatorInflater.loadAnimator(AnimatorInflater.java:106)
System.err:     at android.animation.AnimatorInflater.loadAnimator(AnimatorInflater.java:91)
System.err:     at android.app.FragmentManagerImpl.loadAnimator(FragmentManager.java:1089)
System.err:     at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1368)
System.err:     at android.app.FragmentManagerImpl.moveFragmentToExpectedState(FragmentManager.java:1557)
System.err:     at android.app.BackStackRecord.executeOps(BackStackRecord.java:802)
System.err:     at android.app.FragmentManagerImpl.executeOps(FragmentManager.java:2386)
System.err:     at android.app.FragmentManagerImpl.executeOpsTogether(FragmentManager.java:2181)
System.err:     at android.app.FragmentManagerImpl.removeRedundantOperationsAndExecute(FragmentManager.java:2136)
System.err:     at android.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:2043)
System.err:     at android.app.FragmentManagerImpl$1.run(FragmentManager.java:719)
System.err:     at android.os.Handler.handleCallback(Handler.java:790)
System.err:     at android.os.Handler.dispatchMessage(Handler.java:99)
System.err:     at android.os.Looper.loop(Looper.java:164)
System.err:     at android.app.ActivityThread.main(ActivityThread.java:6494)
System.err:     at java.lang.reflect.Method.invoke(Native Method)
System.err:     at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)
System.err:     at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:807)

@jeremypele - I have same/similar issue in 3.4.1. Happened once randomly while developing, can’t reproduce, and it is happening in the wild.

john-e-riordan on Feb 14, 2018