Loading
Skip execution of transactions on a destroyed activity
An Activity may not yet create on client side, there is another launch request with flags to clear task, then a destroy transaction is scheduled. If client side keeps blocking until destroy timeout, the token on server side will be removed. When client begins to handle the first creation, it will report its activity token to server that causes IllegalArgumentException because there is no matched ActivityRecord. Bug: 32375307 Test: atest FrameworksCoreTests:TransactionExecutorTests Change-Id: I1b7e0c2863b13091c3fd50df602ff31ae02ff38d