Flow: Stack traces

Extensions
26

After pressing the Test4 button on the first invocation, I press the back button ("<", triangle in OS control bar at bottom left of display... )

FirstInvocation-exir
FirstInvocation-exir720×1280 73.2 KB

... just the same as what I understand you to be doing as you describe:

... and then invoke it again by clicking on its icon...

However, if (after exiting as described) I "Force Quit" the app using the app info screen before I re-open it, then it works correctly.

Strange. :confused:

Perhaps I need to run the app on another device or on the emulator...

???,
-Randal

27

Both of the functions were independent.

From what I understand

  1. Open the app, Test1, Test3, Test4 works correctly
  2. You minimise the application, and reenter it again
  3. Now you do Reset + Test 1, but it results in incorrect stack trace (according to you?)

I did the same test, here were my results:

  1. Test1 + Test3 + Test 4

image
image575×1280 88.1 KB

  1. Now I minimised the app using back button, and reenter the app, then I click Reset and Test 1:

image
image575×1280 101 KB

?? It seems to be working fine here

Yes please..

28

Perhaps you can PM me a video recording of this behaviour. I'll be travelling tomorrow for a few days. I'll try to resolve this issue before that.

29

Well, I do, in fact, get different results on a different device:

  1. Original test device: Moto 5e play; Android 8
  2. Second test device: Pixel 3 XL; Android 12

The second invocation of the Pixel 3 screen (Reset+Test3) looks correct:

Screenshot_20250625-131513
Screenshot_20250625-1315131440×2960 161 KB

As a matter of fact, it looks MORE correct than the one you obtain.

Notice that in the above listTraces there appear only those procedures that have been executed on the second invocation, while those from your second invocation (Reset+Test3, quoted below) show the remnants of the FIRST invocation in listTraces in addition to those of the second/current invocation (as does my Moto result):

I

Any idea what is going on? We have 3 different devices with different results.

On two of them it seems that the listTraces contains remnants of the first execution of the app.

More ???,
-Randal