EAS Android build suddenly broke — "no variants exist" for 10 modules, ran out of ideas
Hey everyone, I've been banging my head against this for a full day now and I'm honestly stuck.
My Android release build (eas build --platform android) was working totally fine on July 3rd. Then on July 4th, with literally zero changes to my code or dependencies, it just started failing every single time. All 10 of my native modules (async-storage, firebase, sentry, gesture-handler, svg, and a few others) fail at once with this:
No matching variant of project :<module-name> was found...
- No variants exist.
It's weird because the log doesn't even try to configure these modules before failing — it just jumps straight from configuring expo to the error. On the build that actually worked, those same modules configure and build totally normally.
I've spent way too long trying to figure out what changed:
- Cleared the EAS build cache — no difference
- Turned off Gradle's parallel build setting thinking it might be some race condition — no difference
- Did a full
expo prebuild --cleanand restored my custom native files — no difference - Double checked package.json/package-lock.json are byte-identical between the working build and the broken ones — they are
- Even checked if the builder image itself changed — nope, exact same image both times
The really confusing part is my app builds totally fine locally in release mode on the same commit (fails way later, at an unrelated Sentry step that just needs an env var I don't have locally). So it really does feel like something's off on EAS's side and not in my repo.
Has anyone run into this or have any idea what else could cause something like this? Already filed a support ticket but figured I'd ask here too in case someone's seen it.