Switching between development and release build makes Unity ignore gradle cache
When building for Android, why are the dependencies downloaded and installed with Gradle after building in Development mode lost just because we turn off Development Mode and build again for Release, and vice versa?
If I do other changes to my project, after one build gradle caches the dependencies and it'll build the next time way faster (as in, 2 minutes instead of 40 minutes). However, when I switch from Release to Development mode or the other way around, it builds as if it ignored the cached dependencies (with the 40 minute build time). Even after I've already built in both modes, switching back and forth will always start clean build with cached data ignored.
This can waste so much time when you're in that final day of your production pipeline. Sometimes you need to switch back and forth a couple of times just because you thought it was already ready but when testing on your phone you still spot a bug or two, need to debug in script debug dev mode again, etc.
Your answer
Follow this Question
Related Questions
Moonsharp unity error > Cannot convert clr type 2 Answers
IOS and Android App devopment - Two projects or one? 0 Answers
why chartboost sdk is not integrating to unity? 0 Answers
Unity 2019.2 can't locate ndk or use ndk 0 Answers
icl2pp not building correctly for android.,IL2cpp not building correctly for android. Mono worked. 1 Answer