Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Resource exclusion pattern `org/` silently strips resources from all `org.*` library packages

Open
#21 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
67/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
android, kotlin

Research direction

Start at app/build.gradle.kts:413 and read the resource exclusion block through line 418, including the org/ and .properties patterns. Inspect how these exclusions affect dependency resources, then verify that the narrowed exclusions preserve intended exclusions without stripping unrelated org/ resources when the APK is packaged.

Written by the indexing model from the issue text.

Description

bug

Resource exclusion pattern org/ silently strips resources from all org.* library packages

Severity: High
File: app/build.gradle.kts:413

The packaging resources exclusion block contains:

resources {
    excludes += "META-INF/"
    excludes += "kotlin/"
    excludes += "org/"
    excludes += ".properties"
}

The "org/" pattern is a prefix match against the resource path inside any dependency JAR/AAR. Any library that ships resources under org/ (e.g. org/apache/, org/xmlpull/, org/bouncycastle/ resource files, org/intellij/lang/annotations/) will have those resources silently stripped from the APK.

Why it matters

This is an overly broad exclusion that can cause runtime ClassNotFoundException, FileNotFoundException, or missing-resource crashes in any library whose resources live under org/. If the intent is to exclude only a specific package (e.g. BouncyCastle's pre-computed tables already handled at line 418), the pattern should be narrowed to the specific path like org/bouncycastle/ rather than the entire org/ tree. The same concern applies to the .properties substring match on line 414, which will exclude any file ending in .properties from any dependency — not just META-INF.

Dominant language
Kotlin
Stars
402
Forks
60
Avg merge
4h 8m
Merged PRs (30d)
2

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from wangzhishou/OneBox

All issues in wangzhishou/OneBox

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.