Today I finally resolved my Gradle build issue by switching from Java 21 to Java 17. It turns out that Java 17 is the recommended and supported version even for the most recent Expo SDKs, so this fix lined everything up correctly.
I also followed Expo’s documentation on converting from Expo Go to a development build, which felt like a big step toward getting ARVX closer to production-level structure.
The Gradle error was directly tied to Java version mismatch. After installing Java 17 and updating my environment variables, npx expo run:android finally started working as expected. This was a huge blocker, so clearing it out feels like real progress.
Now I’m tackling my next obstacle: an Android SDK mismatch error. Gradle is complaining about missing or misaligned SDK versions, so I’m digging into Android Studio’s SDK Manager and double-checking my environment variables. This part of setup is tedious, but once it’s stable, I’ll have a much smoother workflow.
Every hurdle gets me closer to having a fully working local Android build. Fixing the Gradle issue was a milestone, and now it’s about ironing out the Android SDK setup so I can keep building with confidence.
Next up: resolve the SDK mismatch and continue shaping out ARVX’s skeleton for mobile.
I’m a fullstack developer passionate about creating dynamic, performant web experiences. Whether it’s a sleek front-end interface or a robust back-end system, I can help bring your ideas to life. Send me a message and let’s get started!
