ResourcesProvider

close

open fun close(): Unit

Frees internal data structures. Closed providers can no longer be added to ResourcesLoader(s).

empty

open static fun empty(assetsProvider: AssetsProvider): ResourcesProvider

Creates an empty ResourcesProvider with no resource data. This is useful for loading file-based assets not associated with resource identifiers.

loadFromApk

open static fun loadFromApk(fileDescriptor: ParcelFileDescriptor): ResourcesProvider

Creates a ResourcesProvider from an APK (.apk) file descriptor.

The file descriptor is duplicated and the original may be closed by the application at any time without affecting the ResourcesProvider.

loadFromApk

open static fun loadFromApk(
    fileDescriptor: ParcelFileDescriptor, 
    assetsProvider: AssetsProvider?
): ResourcesProvider

Creates a ResourcesProvider from an APK (.apk) file descriptor.

The file descriptor is duplicated and the original may be closed by the application at any time without affecting the ResourcesProvider.

The assets provider can override the loading of files within the APK and can provide entirely new files that do not exist in the APK.

loadFromDirectory

open static fun loadFromDirectory(
    path: String, 
    assetsProvider: AssetsProvider?
): ResourcesProvider

Creates a ResourcesProvider from a directory path. File-based resources will be resolved within the directory as if the directory is an APK.

loadFromSplit

open static fun loadFromSplit(
    context: Context, 
    splitName: String
): ResourcesProvider

Read from a split installed alongside the application, which may not have been loaded initially because the application requested isolated split loading.

loadFromTable

open static fun loadFromTable(
    fileDescriptor: ParcelFileDescriptor, 
    assetsProvider: AssetsProvider?
): ResourcesProvider

Creates a ResourcesProvider from a resources table (.arsc) file descriptor.

The file descriptor is duplicated and the original may be closed by the application at any time without affecting the ResourcesProvider.

The resources table format is not an archive format and therefore cannot asset files within itself. The assets provider can instead provide files that are potentially referenced by path in the resources table.

loadOverlay

open static fun loadOverlay(overlayInfo: OverlayInfo): ResourcesProvider

Creates a ResourcesProvider instance from the specified overlay information.

In order to enable the registered overlays, an application can create a ResourcesProvider instance according to the specified OverlayInfo instance and put them into a ResourcesLoader instance. The application calls android.content.res.Resources#addLoaders(ResourcesLoader...) to load the overlays.

finalize

protected open fun finalize(): Unit

Called by the garbage collector on an object when garbage collection determines that there are no more references to the object. A subclass overrides the finalize method to dispose of system resources or to perform other cleanup.

The general contract of finalize is that it is invoked if and when the Java virtual machine has determined that there is no longer any means by which this object can be accessed by any thread that has not yet died, except as a result of an action taken by the finalization of some other object or class which is ready to be finalized. The finalize method may take any action, including making this object available again to other threads; the usual purpose of finalize, however, is to perform cleanup actions before the object is irrevocably discarded. For example, the finalize method for an object that represents an input/output connection might perform explicit I/O transactions to break the connection before the object is permanently discarded.

The finalize method of class Object performs no special action; it simply returns normally. Subclasses of Object may override this definition.

The Java programming language does not guarantee which thread will invoke the finalize method for any given object. It is guaranteed, however, that the thread that invokes finalize will not be holding any user-visible synchronization locks when finalize is invoked. If an uncaught exception is thrown by the finalize method, the exception is ignored and finalization of that object terminates.

After the finalize method has been invoked for an object, no further action is taken until the Java virtual machine has again determined that there is no longer any means by which this object can be accessed by any thread that has not yet died, including possible actions by other objects or classes which are ready to be finalized, at which point the object may be discarded.

The finalize method is never invoked more than once by a Java virtual machine for any given object.

Any exception thrown by the finalize method causes the finalization of this object to be halted, but is otherwise ignored.