IssueTracker

I tested it and it's working as expected for me when starting it the first time:

MainActivity: ProfileInstaller status code: 0
MainActivity: Profile not compiled or enqueued
MainActivity: ProfileInstaller status code: 0
MainActivity: Profile not compiled or enqueued

When running the second time is instead:

MainActivity: ProfileInstaller status code: 0
MainActivity: ProfileInstaller: Enqueued for compilation

As you mentioned, this is correct because ProfileVerifier#getProfileInstallResultCode only verifies if the embedded profile is installed. Since that's the debug version, no profile is embedded and therefore installed.

Instead hasCurrentProfile returns whether there is an existing profile being built. This is normal because ART collected the methods used during first app execution. The profile will be compiled after first bg-dexopt or when manually triggered. At that point also isCompiledWithProfile will return true, even if ProfileVerifier#getProfileInstallResultCode is still 0.

I'm wondering if the solution here is to improve javadocs and documentation? the method getProfileInstallResultCode specifically mentions profileInstall.

Also the javadoc for hasProfileEnqueuedForCompilation states (link):

... an app can have a profile enqueued for compilation because of profile installation through profileinstaller or simply when the user starts interacting with the app ...

As you mentioned, this is correct because ProfileVerifier#getProfileInstallResultCode only verifies if the embedded profile is installed. Since that's the debug version, no profile is embedded and therefore installed.

Having a way to flag that no embedded profile is available would be very helpful. This could be a new status code to flag RESULT_CODE_NO_PROFILE_EMBEDDED or similar. WDYT?

I'm wondering if the solution here is to improve javadocs and documentation? the method getProfileInstallResultCode specifically mentions profileInstall.

Yes, we are currently working to create a guide on profile debugging and verification. That's why this came up.

We can add RESULT_CODE_NO_PROFILE_EMBEDDED. Lemme go ahead and create a task for it.

Created b/313928520

b/313928520 is done. Reassigning this back in case we've to update documentation.

Mark: AFACIT you already addressed the new change in the latest docs update, right?

Yes, this is already live: https://developer.android.com/topic/performance/baselineprofiles/debug-baseline-profiles#installation_issues

Just a heads up that the new version of profile installer hasn't been released yet so those changes are not in the current publicly available version.