diff options
| author | Roshan Pius <rpius@google.com> | 2020-04-06 23:30:23 -0700 |
|---|---|---|
| committer | Roshan Pius <rpius@google.com> | 2020-04-07 06:45:46 +0000 |
| commit | 573e3fe6bef8761f20c75c108acfcceeb41a2e0a (patch) | |
| tree | e310ed8bebb04646f32cabe74f9c918f6148497e /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | f241f952053452a4916a68ef2fe216f4e59fcc97 (diff) | |
WifiNetworkSpecifier: Ensure we don't match a regular wifi network
In Android 10, ClientModeImpl would always attach a
WifiNetworkAgentSpecifier for all wifi network agents created
(regardless of whether it was created in response to a specific request
or not). In Android 11, we changed that behavior to ensure that we
attach the WifiNetworkAgentSpecifier only for agents created in response
to a specific request. However, that is exposing a bug in
WifiNetworkSpecifier matching. WifiNetworkSpecifier attached requests
should not satisfy a generic wifi network agent. Fix the
canSatisfiedBy() matching to ensure that it only matches
WifiNetworkAgentSpecifier (or itself which cannot happen during network
matching)
Bug: 149500993
Test: Add a saved network manually while running the failing ACTS test:
act.py -c wifi_manager_cross.config -tb dut-name -tc WifiNetworkRequestTest:
test_match_failure_with_invalid_ssid_pattern
Test: atest android.net.wifi
Change-Id: I38d154bd0a5685fcc38de891256a8e1d4b8cfbb5
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions