| Filename | Latest commit message | Latest commit date |
|---|---|---|
networkRemoveUidRangesParcel throws ServiceSpecificException if the native network is already destroyed. This can happen when 1) per-app default network request is satisfied by network1 2) unregisterAfterReplacement is called to the network1. This calls netd.networkDestroy and network is removed from netd. 3) per-app default network request is removed. This calls netd.networkRemoveUidRangesParcel but netd does not know about this netid anymore. This CL fixes this issue by skip calling networkRemoveUidRangesParcel if the request satisfier is already destroyed. Bug: 336961452 Bug: 357974842 Test: CSSatelliteNetworkTest Change-Id: Id775cca6fffd03545f1c4bc5016d0de4813f17df |
||
| .. | ||
| android | ||
| com/android | ||