Native unit_tests (and probably other targets) can incorrectly report the current ApplicationState |
|
Issue descriptionSee issue 819592 for a concrete flake caused by this, where the test expects that we are in APPLICATION_STATE_HAS_RUNNING_ACTIVITIES but GetState() reports APPLICATION_STATE_HAS_PAUSED_ACTIVITIES flakily. Notes from conversation with tedchoc: The unit test should run NativeUnitTestActivity, which should be calling ApplicationStatus#initialize Might make sense to add logging to initialize, the test code, and onCreate in ApplicationStatus (when the activity is created). |
|
►
Sign in to add a comment |
|
Comment 1 by tedchoc@google.com
, Mar 13 2018