You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 26, 2024. It is now read-only.
I'm from Beacon team, and we have a 'Beacon SDK' which is a collection of AARs that different partners integrate to get user location. So, if with each check-in we start to get size impact on these AARs , then it could be quite useful to us. We'll be happy to get just the total size of AARs to start with.. You already seem to have a system in place to check and report the APK file size, the same would work for AAR to start with. You can search for .AAR files built in the build directory and report the sizes of all or of just those that are in the release folder. I'm sure this would be useful for many other size conscious teams as well, including my previous team where we started a process of including AAR size as part of daily manual testing report to get a feel of how our SDK size was getting impacted each day.
The text was updated successfully, but these errors were encountered:
Thanks for the first feature request @mokhanna1. At the moment, the extension takes file paths to 2 APK files - before and after changes. Just to make sure I understand the requirement, are you suggesting analyzing the AAR files in the build directory before and after changes?
Or is it analyzing a single AAR file?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm from Beacon team, and we have a 'Beacon SDK' which is a collection of AARs that different partners integrate to get user location. So, if with each check-in we start to get size impact on these AARs , then it could be quite useful to us. We'll be happy to get just the total size of AARs to start with.. You already seem to have a system in place to check and report the APK file size, the same would work for AAR to start with. You can search for .AAR files built in the build directory and report the sizes of all or of just those that are in the release folder. I'm sure this would be useful for many other size conscious teams as well, including my previous team where we started a process of including AAR size as part of daily manual testing report to get a feel of how our SDK size was getting impacted each day.
The text was updated successfully, but these errors were encountered: