Count methods for the test apk
See original GitHub issueIn kotlin, rxjava era having single dex only limitation for the test-apk emerges the need to control methods count for the project androidTestImplementation
dependencies.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:8
Top Results From Across the Web
How to determine application's method count? - Stack Overflow
To get a method-count report on every build, do this: ... There is a tool APK method count which counts the number of...
Read more >APK method count
Drop file here to load content or click on this box to open file dialog. No file will be uploaded - uses only...
Read more >Analyze your build with APK Analyzer - Android Developers
The Referenced Methods column counts all methods that are referenced by the DEX file. This typically includes methods defined in your code, ...
Read more >Output per-package method counts in Android APK - GitHub
Output per-package method counts. Supports multidex. Also you can now view per-class method counts for more detailed analysis. Inline classes are showed in...
Read more >Jetpack Compose — Before and after | by Chris Banes - Medium
We see a 41% reduction in APK size, and 17% reduction in method count when ... For this test I used the cloc...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’m not sure that I understand the issue; let me rephrase, and tell me if I got it right:
Test APKs are limited to a single .dex file. When using large libraries like rxjava and kotlin-stdlib, it’s easy to go over the limit. Therefore, we need to add the ability to count methods in test APKs.
Is that right? If so, I can’t think off-hand how that might be implemented. Any ideas?
Given that I don’t have much discretionary time to spend, I’m going to close this as won’t-fix. It sounds like this may be a) a pre-Lollipop issue, and b) work-aroundable.