MissingSplitsManager

disableAppIfMissingRequiredSplits

public abstract boolean disableAppIfMissingRequiredSplits ()

This method is deprecated.
the feature is now obsolete. Installs with missing splits are now blocked on devices which have Play Protect active or run on Android 10.

If your app is missing a required split APK, this API gracefully closes the app. Additionally, if the app is started by an explicit user action, the user is informed that the app is not installed correctly.

Using this API might include the following side effects:

• If a required split APK is missing, disables all non-activity app components.
• if no required split APK is missing and all non-activity components are currently disabled (indicating that their state was manipulated by PlayCore), resets all non activity app components to their default enabled state.
• Stops the current OS process (including explicitly cancelling all app tasks via ActivityManager.AppTask.finishAndRemoveTask()) and starts a new OS process for PlayCoreMissingSplitsActivity.

For examples of typical use cases, including usages in Application.onCreate(), see Check for missing app components.

isMissingRequiredSplits

public abstract boolean isMissingRequiredSplits ()

This method is deprecated.
the feature is now obsolete. Installs with missing splits are now blocked on devices which have Play Protect active or run on Android 10.

Checks whether the app is missing a required split APK, without any side effects, such as disabling the app.

You should typically use this API to manually skip initialization logic of custom ContentProvider implementations. That's because ContentProvider instances are initialized before the Application.

For examples of typical use cases, including usage in ContentProvider.onCreate(), see Check for missing app components.