rbro112
commented
8 months ago Unfortunately this is a more complicated issue that will require some bigger changes to solve. Immediately, the easiest workaround to this problem is to simply name the performance project a name which will come after the main app module's alphabetically (i.e. if app module's name is :terrificapp, the performance module would need to come after it alphabetically, i.e. :terrificperformance).
We have long-term plans to address this in a future major version of our Gradle plugin.
A client recently experienced this and set up a repro: https://github.com/ivanalvarado/EmergeTools-Perf-Analysis-Reproducer
After further investigation, it seems Gradle's project resolution runs in an alphabetical manner, so when the performance module's name comes before the app module's name alphabetically, we experience this issue.