Initialize customMemoryBackingFiles with empty array
which was introduced in aosp/3426231
Bug: 395716159
Test: run terminal app
Change-Id: I84615472e74ac40b2d64f6dcbfbd3f6f816e49f6
diff --git a/libs/framework-virtualization/src/android/system/virtualmachine/VirtualMachineConfig.java b/libs/framework-virtualization/src/android/system/virtualmachine/VirtualMachineConfig.java
index 83b234d..2668ca2 100644
--- a/libs/framework-virtualization/src/android/system/virtualmachine/VirtualMachineConfig.java
+++ b/libs/framework-virtualization/src/android/system/virtualmachine/VirtualMachineConfig.java
@@ -42,6 +42,7 @@
import android.sysprop.HypervisorProperties;
import android.system.virtualizationservice.AssignedDevices;
import android.system.virtualizationservice.CpuOptions;
+import android.system.virtualizationservice.CustomMemoryBackingFile;
import android.system.virtualizationservice.DiskImage;
import android.system.virtualizationservice.Partition;
import android.system.virtualizationservice.SharedPath;
@@ -835,6 +836,7 @@
})
.orElse(null);
config.teeServices = EMPTY_STRING_ARRAY;
+ config.customMemoryBackingFiles = new CustomMemoryBackingFile[0];
return config;
}