The Android Developer Challenge is back! Submit your idea before December 2.

Play Core Library release notes

When you publish your app with an Android App Bundle, Google Play’s Dynamic Delivery allows your app to download dynamic feature modules on demand to devices running Android 5.0 (API level 21) and higher. Your app simply needs to call APIs in the Play Core Library to download and install those modules, and the Google Play Store pushes only the code and resources needed load that module on the device. You can also use this API to download on demand modules for your Android Instant Apps.

To learn how to first add dynamic feature modules to your project and configure them to be available on demand, read Create a dynamic feature module.

If you want to see the Play Core Library in action, try the Play Core Library sample app.

This page explains how to keep the library up to date and what's in the recent updates.

Include the Play Core Library in your project

Before you can start using the Play Core Library, you need to first import it into your app module as a Gradle dependency, as shown below:

// In your app’s build.gradle file:
...
dependencies {
    // This dependency is downloaded from the Google’s Maven repository.
    // So, make sure you also include that repository in your project's
    // top-level build.gradle file.
    implementation 'com.google.android.play:core:1.6.4'
    ...
}

1.6.4 (October 2019)

New features

  • Adds FakeSplitInstallManager, which you can use for testing dynamic feature module install in integration tests, without connectivity.
  • Javadoc and IntDef annotations are now exported in the maven repository, providing Android Studio completion, etc.
  • Kotlin extensions now available in alpha. Add com.google.android.play:core-ktx:1.6.4 as a module dependency and include import com.google.android.play.core.ktx.* in your code.
  • You can now initiate in-app update flows from fragments (in addition to activities).

1.6.3 (September 2019)

This release includes general bugfixes.

1.6.2 (September 2019)

New features

  • Adds a new API SplitCompat.installActivity for installing SplitCompat on activities. This has better performance than calling full SplitCompat.install on the activity.

Behavior changes

  • Native code fix for loading certain libraries on certain devices
  • More robust recovery from interrupted SplitCompat
  • More useful information in the string representation of exceptions
  • Other general bugfixes and updated JavaDocs

1.6.1 (July 2019)

This release includes general bugfixes.

1.6.0 (May 2019)

New features

  • New Sideloading crash prevention API, which allows you to detect incomplete installation of apps that are built using an Android App Bundle. To learn more, read Verify non-Google Play app installs.

1.5.0 (April 2019)

New features

  • New In-App Update API, which allows you to request users to trigger an update directly from the app. To learn more, read Support in-app updates.

1.4.1 (April 2019)

Behavior changes

  • Fixes multi-process race condition in SplitCompat
  • Better background thread management

1.4.0 (February 2019)

New features

1.3.7 (February 2019)

New features

  • Adds explicit error codes for SplitCompat failure scenarios
  • Adds the startIntentSenderForResult() method to start the confirmation dialog. Using the PendingIntent directly has been deprecated. To learn more, read Obtain user confirmation

Behavior changes

  • Fixes race conditions in SplitCompat that, in rare occasions, lead to errors
  • Fixes bug in SplitCompat where, in the rare case that the app had no configuration splits, modules were not reported as installed

1.3.6 (November 2018)

New features

  • New INSUFFICIENT_STORAGE error when installs cannot complete due to lack of disk space

Behavior changes

  • A module is now reported as installed only if its master split is installed (previously any split would suffice)
  • Mixed case class names are no longer used, which sometimes caused issues when building on Windows