Loading
[PIP] Split implementation of isPackageActiveInPip for PIP1 and PIP2
This reverts a change made to isPackageActiveInPip() for PIP1 to fix an issue where we never reset lastPipComponentName. We still need to investigate this behavior for PIP2 as there are changes in core that affect how TransitionInfo is being constructed. Bug: 379013276 Flag: EXEMPT bugfix Test: manually follow steps in bug report, verify split starts properly Change-Id: Ie66d5d3efbba13c649dbd63670625b155eeef30d