skiptools / skiptools/skip-keychain
Building release app with skip-keychain raises error: "Missing classes detected while running R8" for com.google.errorprone.annotations.Immutable
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 10
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
The following error will occur when building an app that depends on skip-keychain in release mode (e.g., using fastlane assemble from the Android/ folder):
ERROR: Missing classes detected while running R8. Please add the missing classes or apply additional keep rules that are generated in /opt/src/github/skiptools/skipapp-notes/.build/Android/app/outputs/mapping/release/missing_rules.txt.
ERROR: R8: Missing class com.google.errorprone.annotations.Immutable (referenced from: com.google.crypto.tink.KeyTemplate and 11 other contexts)
> Task :app:minifyReleaseWithR8 FAILED
w: Detected multiple Kotlin daemon sessions at
[Incubating] Problems report is available at: file:///opt/src/github/skiptools/skipapp-notes/.build/Android/skip.notes/reports/problems/problems-report.html
This is reported at https://github.com/tink-crypto/tink-java/issues/7. The recommended workaround to add the following rules to the Android/app/proguard-rules.pro file seems to work:
-dontwarn com.google.errorprone.annotations.CanIgnoreReturnValue
-dontwarn com.google.errorprone.annotations.Immutable
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with Android/app/proguard-rules.pro and reproduce the release build using fastlane assemble from the Android/ folder. Compare the R8 missing-classes output with the referenced Tink issue and verify that the release build completes without the com.google.errorprone.annotations errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android
- Domain
- build-system, mobile
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100