Do not restart process of a finishing activity
The destruction operation should have higher priority. That also avoids disturbing DESTROYING state when the client reports destroyed. Currently some callers of restartProcessIfVisible such as ActivityTaskManagerInternal and TaskOrganizerController also ignore finishing activity. So this just adds a double check for the path from config change. Bug: 276467485 Test: CompatChangeTests Change-Id: Icd24147abb1d4e5859c44862ed42f4557ecb2387
Loading
Please register or sign in to comment