Fixing tabOwnerUserHandle population.
b/266175872 points out the case where personal handle may be populated differently than the callingUserId. In such cases tabOwnerUserHandle should be in sync with the current process' userHandle rather than the callingUserId. Bug: b/266175872 Test: atest ResolverActivityTest Change-Id: Ia3521a8878d6e7b7de891ef4f4b09c5766d12a74
Loading
Please register or sign in to comment