Android Library模块中assets目录是否允许？实测与官方说明存疑

Hey there, great question—this is a common point of confusion, so let’s break it down clearly:

• Yes, including an assets directory in your Android Library module is fully allowed and officially supported
  When you build your library into an AAR file, the assets folder and all its contents will indeed be packaged into the AAR, just like you observed. This is intentional behavior, and many popular third-party libraries rely on this to distribute raw files like fonts, preloaded datasets, HTML content, or other unprocessed resources.

• Clarifying the "no raw assets" note you mentioned
  The confusion might come from older documentation or a mix-up with resource handling rules. Android does have specific rules for res/ directory resources (like drawables or strings) in libraries, but assets are treated differently. Unlike res resources (which are compiled and merged with priority given to the app module), assets are bundled as raw files and merged into the app’s assets directory during the build process (if there’s a filename collision, the app module’s asset will override the library’s).

• Practical use cases for library assets
  This approach is perfect when you need to distribute files that don’t fit into the structured res/ system—for example:

  • Custom font files that don’t use the modern font resource system
  • Pre-built HTML/CSS/JS for in-app web views
  • Binary data files (like SQLite databases) that need to be copied to the device’s storage at runtime

So to wrap it up: Your test result is exactly what’s expected, and there’s no issue with including assets in your Android Library module. Go ahead with this approach confidently!

内容的提问来源于stack exchange，提问作者user1506104