Is there a cache somewhere for the schema and/or queries? I'm having a problem when switching from a branch that has new queries and types added to schema to one that doesn't contain them. I have

generateTestBuilders.set(true)

(though I tried turning that off, that didn't work either) and I keep on getting errors from a TestBuilder for the queries from my other branch, that the classes don't exist.

Hmm it could be a Gradle build cache issue? Do you have this on the command line as well or only in the IDE?

In both, after trying ./gradlew clean as well

haha yeah I can imagine! Weird! What about with

--no-build-cache

?

Same problem 😞

I had some caching issues unrelated to Apollo that were resolved by removing the

.gradle

directory in the project root directory and running a clean/build, maybe it'll help in your case too

Running gradle with

-i

shows some useful information (sometimes a bit too much but each task is usually in bold making it easier to troubleshoot). In a case like this, after switching branches, I would expect

generateApolloServiceSource

to be re-run (i.e. not up-to-date) because some input graphql files were removed.

I think @wasyl wins the price (only honour, unfortunately) 🏆 I removed my gradle cache (and then I had to update my gradle version as well 🤷‍♀️), and now things work again. Thanks everyone for chipping in with suggestions!