DataStoreFactory

public final @NonNull DataStore<@NonNull T> <T extends Object> create(
    @NonNull Serializer<@NonNull T> serializer,
    ReplaceFileCorruptionHandler<@NonNull T> corruptionHandler,
    @NonNull List<@NonNull DataMigration<@NonNull T>> migrations,
    @NonNull CoroutineScope scope,
    @NonNull Function0<@NonNull File> produceFile
)

Create an instance of SingleProcessDataStore. Never create more than one instance of DataStore for a given file; doing so can break all DataStore functionality. You should consider managing your DataStore instance as a singleton. If there are multiple DataStores active, DataStore will throw IllegalStateException when reading or updating data. A DataStore is considered active as long as its scope is active.

T is the type DataStore acts on. The type T must be immutable. Mutating a type used in DataStore invalidates any guarantees that DataStore provides and will result in potentially serious, hard-to-catch bugs. We strongly recommend using protocol buffers: https://developers.google.com/protocol-buffers/docs/javatutorial - which provides immutability guarantees, a simple API and efficient serialization.

It is important to note that if a produceFile lambda to produce a file in the User Encrypted (UE) storage via a Context is used, this file will not be available during direct boot, and may result in a DirectBootUsageException via a java.io.FileNotFoundException or a silent failure. To create an instance of a DataStore to be used safely during direct boot mode, please use createInDeviceProtectedStorage.

public final @NonNull DataStore<@NonNull T> <T extends Object> create(
    @NonNull Serializer<@NonNull T> serializer,
    ReplaceFileCorruptionHandler<@NonNull T> corruptionHandler,
    @NonNull List<@NonNull DataMigration<@NonNull T>> migrations,
    @NonNull CoroutineScope scope,
    @NonNull Function0<@NonNull File> produceFile
)

Create an instance of SingleProcessDataStore. Never create more than one instance of DataStore for a given file; doing so can break all DataStore functionality. You should consider managing your DataStore instance as a singleton. If there are multiple DataStores active, DataStore will throw IllegalStateException when reading or updating data. A DataStore is considered active as long as its scope is active.

T is the type DataStore acts on. The type T must be immutable. Mutating a type used in DataStore invalidates any guarantees that DataStore provides and will result in potentially serious, hard-to-catch bugs. We strongly recommend using protocol buffers: https://developers.google.com/protocol-buffers/docs/javatutorial - which provides immutability guarantees, a simple API and efficient serialization.

@RequiresApi(value = 24)
public final @NonNull DataStore<@NonNull T> <T extends Object> createInDeviceProtectedStorage(
    @NonNull Context context,
    @NonNull String fileName,
    @NonNull Serializer<@NonNull T> serializer,
    ReplaceFileCorruptionHandler<@NonNull T> corruptionHandler,
    @NonNull List<@NonNull DataMigration<@NonNull T>> migrations,
    @NonNull CoroutineScope scope
)

Create an instance of SingleProcessDataStore that can be used during direct boot.

This API always creates the DataStore in the Device Encrypted storage.