When the time flow control buttons are already active/displayed on startup of SS7 and when starting a time flow with the arrow buttons, I cannot stop the flow by pressing any of the control buttons. I see this on my iPad Pro and iPhone 11, both iOS 15.2.x.
I need to deactivate the time flow control toolbar and reactivate it in order to stop the time flow with the arrow buttons.
Did anybody else notice this unexpected behavior?
Never had this issue with SS6.
DevOps reference: https://starrynight.unfuddle.com/a#/projects/7965/tickets/by_number/1717
Confirmed. Thanks Wilfred.
How do you get time flow stuck? It seems to work well for me.
bruce
It is only stuck when the time control buttons are already active when you start up / open the app. Activate the time flow control. Close the app completely and re-open it.
Okay, I started time flow at 5 seconds per step. Closed the app. Tossed the app. Reopen the app. It reopened with time stopped where it was closed. I do not have anything else open on my iPad Pro. iOS 15.2.1.
Maybe I’m not following.
bruce
But if I start time flow and just close the app and then reopen the app it picks up from where it left off on close with time flow on. Perhaps you are saying that it keeps running when the app is closed and time flow keeps going forward. That is weird
bruce
You are almost there ;-)
The time flow controls need to be active, i.e. on display before closing the app. An actual time flow does not need to be running. It’s only about the controls being active, not the actual flow.
Then you close the app completely.
Then re-open the app. The time flow controls should still be visible.
Then start a time flow by pressing (i.e. actually touching!) any of the on-display arrow buttons (forward or backward).
In my case, I cannot stop the time flow by re-touching any of the arrow buttons or the “now” button. I have to close the time flow controls by touching the time icon in the top-left corner, re-open the controls and touch an arrow button.
This “only” applies to SkySafari 7.x, not version 6.x.
this is super annoying, when will it be fixed?