title: Build problems: Faulty Smali code on one machine/account working APK on another
body: <p>I have two user accounts on Ubuntu 22.04, Android Studio (and all build tools installed on both. For my main account everything works, on the other, the Android app builds fine but <strong>behaves differently</strong>. This wrong behavior only occurs when building the app on my main account, but not when someone else builds it or the CI runner creates an APK.</p>
  <p>It does not matter whether I build it from the command line or from within Android Studio.
  I am desperately looking for an explanation or even for ways to debug this. Isn't there some command that prints all environment variables, all paths to all tools, configs, etc… involved in the build process to give me <em>some</em> clue as to what is going on?</p>
  <p>This issue only affects building Android apps. Building other JVM-based software (Spring, even mixed Kotlin+Java sources, traditional JEE services) works perfectly fine.</p>
  <p>I copied the project folder to other machines, set up a VM, and freshly checked everything out from git and the same reproducible behaviour occurs: Building on my main machine results in a runnable Android app, which exhibits bugs <strong>that do not exist in the source code or in the libraries used</strong>, building it <strong>anywhere else</strong> results in an app, which behaves as it should. We even verified that building the app on my main account produces different smali code compared to any other build setups.</p>
  <p>I tried manually installing the Android SDK, tried managing it from within Android Studio installed from the JetBrains, flathub, snap store… no dice.</p>
  <p>How to debug this?</p>