Skip to content

Merge layouts  #44

@gpallas16

Description

@gpallas16

What are the steps to reproduce this issue?

  1. Create project A and add some layouts
  2. Import project A's aar to project B. All layouts from project A are accessible as expected.
  3. Create fat aar with project A and project B
  4. Import fat aar to project C. The layouts from project A are not accessible and app crashes if some class from project B uses a layout from project A (which was working normally before the fat aar) . All project B layouts are accessible.

What happens?
The layout files are in .aar/class.jar/res/layout and not in .aar/layout. The R file from project A is missing too. I use minifyEnabled true with no shrinking and no optimizations. I am relatively new to aar so I dont know if this is a bug or I m missing something. Any advice would be nice!

I use gradle 3.2.0 and fat-aar version 2.0.2

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions