Re-implement NetworkUtils#queryUserAccess.
Currently, queryUserAccess talks to netd via FwmarkServer. Doing this from the module would require exposing queryUserAccess as an NDK API or reimplementing FwmarkClient. Because queryUserAccess really only uses information that comes from ConnectivityService/PermissionMonitor anyway, just use that information without calling to net. Test: atest HostsideVpnTests Bug: 171540887 Change-Id: If855de1ea3e1fd2ed30f2795d9b4acfcf969a2dc
This commit is contained in:
committed by
Remi NGUYEN VAN
parent
0da9e8b1e7
commit
d81932b836
@@ -1556,7 +1556,7 @@ public class ConnectivityServiceTest {
|
||||
doReturn(mNetworkStack).when(deps).getNetworkStack();
|
||||
doReturn(mSystemProperties).when(deps).getSystemProperties();
|
||||
doReturn(mock(ProxyTracker.class)).when(deps).makeProxyTracker(any(), any());
|
||||
doReturn(true).when(deps).queryUserAccess(anyInt(), anyInt());
|
||||
doReturn(true).when(deps).queryUserAccess(anyInt(), any(), any());
|
||||
doAnswer(inv -> {
|
||||
mPolicyTracker = new WrappedMultinetworkPolicyTracker(
|
||||
inv.getArgument(0), inv.getArgument(1), inv.getArgument(2));
|
||||
|
||||
Reference in New Issue
Block a user