IssueTracker

Baseline profiles also participate in the obfuscation process, like classes; so this already works.

Do you mean the functions & classes recorded by the baseline's benchmark test are refactored with the new obfuscated ones when the minification task is completed?

That is correct.

Great! Thanks for the update!

Just a clarifying update. The mapping of the baseline profiles use the R8 mapping file to map from the input to the output. As the mapping file is not designed for mapping in that direction the mapping will not always be complete but use a "best effort" approach. This usually give good results, but can miss some items in the profile.

Does that mean we should expect the baseline-prof.txt file (the one that is generated on a device and copied as a sibling of AndroidManifest.xml in the main source set) to not contain obfuscated class names? Is the minification Gradle task taking care of mapping that file to correct values when bundling a binary version of the baseline profile in the app artifact?

That is correct.

Is there any harm in generating the baseline profile with obfuscation turned on?

Is there any harm in generating the baseline profile with obfuscation turned on? Because in this article https://developer.android.com/topic/performance/baselineprofiles/create-baselineprofile#create-new-profile don't say anything about obfuscation turn off, when I do it via baselineProfile module.