This message was deleted.

This property is injected by android studio based on the target emulator. I recommend running builds using the command line to avoid this issue

Interesting. Running the same

:app:assembleProdDebug

command via the command line took 11s. That is once I had ran it once to get the daemon up and running. This then leads me to 2 questions : 1. Is there a way to get some command line output similar to the analyzer output? 2. Is there some documentation repo that would give me more insight into dexParams and perhaps the things android Studio does that aren't immediately obvious? Thanks for your response.

A build scan is a much more detailed report of what happened during your build. https://scans.gradle.com/

No worries. Thank you for your time and help in understanding the problem. Re: build scans I'm not sure that we can use them because some of the build data is made public. If I keep chasing the client then we may get there in the end. Thanks

Hey @no, in a scenario where we have remote build cache and most of the developers build the project through AS, do you think it’s worth building on CI with injected properties too?

That's a good question. I think it depends on your scenario. I would say run an experiment to see how much time it saves and if it is worth the compute resources.

I’ll do that and bring you my results

Yes please! I would be very interested to see 🙂