Autobuild ignores default build variant setting for Android projects

[tmo1]

CodeQL autobuild apparently always tries to build the alphabetically earliest build variant for an Android project, ignoring alternate default build variant settings specified in build.gradle:

• https://issuetracker.google.com/issues/36988145
• https://stackoverflow.com/questions/52072162/how-to-change-android-studios-default-build-flavor

For example, my project SMS Import / Export has four build variants, and the default is set to standardDebug. Android Studio respects this, but CodeQL autobuild still tries to build legacyDebug.

[rvermeulen]

Hi @tmo1

Thanks for your question. We will investigate this and follow up with an update.

[rvermeulen]

Hi @tmo1

Could you share the logs created in the database directory of the project that isn't build correctly so we can further investigate?

[tmo1]

I assume this is what you want - please let me know if there's anything else I should provide.

[smowton]

CodeQL autobuild simply runs gradle assemble when faced with an Android project. What Gradle target or flags would you normally pass to get your preferred variant to build? I expect for this project you'll need to switch to a manual build and specify an appropriate command: https://docs.github.com/en/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/codeql-code-scanning-for-compiled-languages#specifying-build-commands

[tmo1]

What Gradle target or flags would you normally pass to get your preferred variant to build?

As per the Google Issue Tracker and Stack Overflow links in my original post, Android Studio can use stanzas like getIsDefault().set(true) in build.gradle to invoke Gradle with the appropriate build variant specification. I'm suggesting that CodeQL autobuild should do so as well.

[rvermeulen]

Hi @tmo1,

Thanks for the feedback, we will share this with the team.
To remediate your current issue it is best to migrate to a manual build step as adviced by @smowton.

[tmo1]

Okay - thank you!