Don't add LOCAL_NETWORK as forbidden capability
This causes the module to crash on rollback because the current production code does not consider LOCAL_NETWORK to be a valid capability. Change-Id: Idf57d72c384b41b483098c4c302738072ebf7f90 Test: TH Fix: 313030307
This commit is contained in:
committed by
Remi NGUYEN VAN
parent
dbae5744a1
commit
22941b38f7
@@ -290,7 +290,10 @@ public class NetworkRequest implements Parcelable {
|
||||
* Therefore these capabilities are only in NetworkRequest.
|
||||
*/
|
||||
private static final int[] DEFAULT_FORBIDDEN_CAPABILITIES = new int[] {
|
||||
NET_CAPABILITY_LOCAL_NETWORK
|
||||
// TODO(b/313030307): this should contain NET_CAPABILITY_LOCAL_NETWORK.
|
||||
// We cannot currently add it because doing so would crash if the module rolls back,
|
||||
// because JobScheduler persists NetworkRequests to disk, and existing production code
|
||||
// does not consider LOCAL_NETWORK to be a valid capability.
|
||||
};
|
||||
|
||||
private final NetworkCapabilities mNetworkCapabilities;
|
||||
|
||||
Reference in New Issue
Block a user