Accelerate your construct: Non-transitive R information

Non-transitive R information become to be had to all modules in AGP 4.2. Non-transitive R information permit your builds to be incrementally quicker and your AAB/APK’s smaller. This publish will provide an explanation for tips on how to enforce and construct your app with non-transitive R information.

Non-transitive what?

In arithmetic, non-transitivity is a assets of binary family members that aren’t transitive family members. This may increasingly come with any relation that’s not transitive, or the more potent assets of antitransitivity, which describes a relation this is by no means transitive.

Does that math quote is helping us in any respect? Most definitely no longer. Let’s do this: If A depends upon B and B depends upon C, A does no longer learn about C. On this planet of Android, non-transitive R information:

Non-transitive R categories permit namespacing of every library’s R magnificence in order that its R magnificence contains most effective the assets declared within the library itself and none from the library’s dependencies, thereby decreasing the dimensions of the R magnificence for that library.

This weblog publish isn’t about how the R record works and the historical past concerned, if you have an interest within the background I’d counsel this weblog publish right here.

Non-transitive modules

If module A depends upon B and B depends upon C. How are we able to reference assets? Let’s see:

Module A can reference its personal assets (like customary):


Module A can reference Module B assets (totally certified package deal):

Module A can not reference Module C‘s assets.

You’ll be able to use non-transitive R categories with the Android Gradle plugin (>4.2) to construct quicker builds for packages with more than one modules. … This ends up in extra up-to-date builds and the corresponding advantages of compilation avoidance.

Advantages of non-transitive R categories?

  • Lower in AAB/APK measurement, together with DEX box reference rely
  • Lower in incremental construct velocity as much less dependencies will also be integrated when adjustments made
  • Building up in modularity, dependencies grow to be extra specific
  • Lower in complexity, assets can not come from transitive dependencies
  • Lower in complete construct length as much less code integrated

Let’s do it!

You’ll be able to flip this surroundings on for your self by means of enhancing your /gradle.houses record to incorporate:


You will have examine android.namespacedRClass up to now. Observe that during August 2020; android.namespacedRClass assets used to be renamed to android.nonTransitiveRClass. As proven right here.


You’ll be able to use the Android Studio automatic refactor, this may flip at the above surroundings and seek via your modules making an attempt to completely qualify any R references it unearths.

Observe that this refactor used to be added in Android Studio Arctic Fox | 2020.3.1 “automatic refactoring for non-transitive R information”. As proven right here.

Android Studio > Refactor > Migrate to Non-Transitive R Categories…

This auto-refactor isn’t a silver bullet, it is going to get some useful resource references incorrect, i.e. it’ll upload the incorrect package deal identify earlier than the R magnificence or it is going to fail to make a choice one in any respect, or it’ll upload person who your module doesn’t have a dependency upon. In my revel in those problems are stuck at construct time, and you’ll make a choice from the 3 answer steps underneath, to complete off what the refactoring software began:

As soon as this is performed, you’ll have to construct your venture and connect the mistakes. Mistakes can are available a couple of codecs:

  1. You employ a useful resource from some other module.
    Repair: upload the totally qualifed package deal, or import the R record, or (Kotlin most effective) use an alias.

    // Totally qualifed package deal
    val foo =
    // Import then use string.hello_neighbour
    // Alias then use RB.string.hello_neighbour
    import as RB

  2. You employ a useful resource from some other module, however you don’t claim as dependency on that module.
    Repair: Do as #1 but in addition upload the dependency in gradle.

    implementation venture(":libraries:moduleB")

  3. You employ a useful resource from some other module, however you don’t claim a dependency on that module, and you do not need to claim a dependency.
    Repair: The answer here’s to both generate a reference and use the similar identify or replica/create a brand new useful resource of what you need.
Generate a reference to your module, when the implementation is in some other “transitive” module.


That’s all there’s too it, which is relatively simple for me to mention however in apply relying at the measurement of your venture, you might have many hours forward of you, debugging/looking the place your assets come from and what’s the right kind totally certified package deal identify to make use of. I’d extremely counsel for any new initiatives you activate nonTransitiveRClass earlier than you must take care of the fallout down the road.

You May Also Like

More From Author

+ There are no comments

Add yours