So @tiwag, what you could do, is to confirm if this is also for you a way to replicate the bug:
I’ve found that re-opening the app from the list of apps in the background, and from the widget have the same outcome.
So @tiwag, what you could do, is to confirm if this is also for you a way to replicate the bug:
I’ve found that re-opening the app from the list of apps in the background, and from the widget have the same outcome.
So @tiwag, what you could do, is to confirm if this is also for you a way to replicate the bug:
0942 CEST : test is running …
1016 CEST : re-opening flowx from the list of apps in the background
it behaves slightly different
maybe this has something to do with the last app update ?
maybe this has something to do with the last app update ?
no it doesn’t , the workaround works when opened flowx by tapping the widget.
There is a different behaviour of flowx, if either the app is opened from background or from the widget.
The main problem is of course the same
Hm, interesting. I was wondering why your workaround did not seam to work for me.
My default behavior have developed to become that more or less every time i open Flowx, I immediately close it again, and then re open it from the widget, since almost always i have had Flowx opened sine before, so that it has been running in the background.
The “swipe to close, and tap widget to reopen”-routine has become faster for me than performing a forced refresh. By now it’s a habit so strong that sometimes I do it when I don’t have to…
By now it’s a habit so strong that sometimes I do it when I don’t have to…
Somehow “drilled by flowx”
The “swipe to close, and tap widget to reopen”-routine has become faster for me
this is my procedure now too
thanks for the tip !