(android) Navigation does not work when the app is started while the device is locked about nativescript-angular HOT 4 OPEN

@facetious does this not happen with core NativeScript? I know that core stops all native updates when the screen is off, so it's probably some native updates that aren't being applied.

from nativescript-angular.

@edusperoni I actually don't know. I encountered this issue because I typically have the phones locked on my desk, then unlock them when I'm testing something out. These navigations aren't triggered while the screen is locked; I am tapping on something on screen, the Angular tracing agrees, and any trace messages in put in the to-be-shown component appear as though it was presented on screen. But the screen doesn't actually navigate. The app isn't frozen; I can tap on other things and have more Angular tracing logs come out, but still no navigation.

from nativescript-angular.

Disappointingly, when I have tried to reproduce this quickly in a fresh project, it doesn't happen. So I'm going to have to figure out what complicated sequence of failures has caused this to happen in my app.

from nativescript-angular.

I have narrowed this issue down to an explicit navigation that is being made (after the initial Angular routing settles). If I delay the automatic "go to the next screen" until the app is in the foreground, everything operates normally. It should be possible to create a small project exhibiting this behaviour with this understanding.

from nativescript-angular.