Hello, allow me to resurrect this thread because I'm observing the same behaviour.
Whenever you're navigating to the 'Previous screen', and that previous screen is the one set as the Default screen.
Samuel is going around this by having an automatic redirect from a (blank)Default screen to a secondary, actual 'Home' screen, bypassing the problem.
It's still a workaround, and this looks like a bug to me.
From my investigation, what I could observe is the OnApplicationReady running every time I hit the Default screen. The glitch is happening even if you're not using an OnApplicationReady, so it makes me think the platform might be running some other scripts again which should run only once when you open the app.
I attached an oml with a very simple example of this. The module is absolutely default, has 3 screens and just a few buttons.
If you do this pattern:
Home Screen > Screen A > Screen B > Home Screen > Screen A
and then start hitting the button with the 'Previous screen' link
Screen A > Home Screen > Screen B > Screen A ~glitchy transition~> Home Screen
So it's not the screen itself, but when it is the final node in this backward navigation.
It's not platform breaking but this is pretty annoying and puts a dent on the user experience. Any hints?