It's possible to use apollo3 and an older version ...
# apollo-kotlin
c
It's possible to use apollo3 and an older version of apollo in the same app, right?
b
yes, they are in separate packages
c
Interesting. I'm trying to write a query today in an existing project and I get this error on
query
Copy code
Cannot access 'java.io.Closeable' which is a supertype of 'com.apollographql.apollo3.ApolloClient'. Check your module classpath for missing or conflicting dependencies
Yesterday, when i was experimenting with apollo3 in a new project, i had no issues. so im confused on what the issue could be. hmmmm....
m
Is that in your IDE or at build time? I've seen this in the IDE if the project SDK doesn't match... something
c
Its in my IDE
m
Tweak your project settings until it works
THere are a bunch of YouTracks (like this one) but it's unclear if this was fixed (looks like it's not)
c
oh. it seems like my code compiles. its just the IDE...
w
There’s a workaround that used to work in Android Studio, maybe it’ll help you too https://issuetracker.google.com/issues/213131387
Specifically
Removing the
options/jdk.table.xml
file, located in
~/Library/Application Support/Google/AndroidStudioPreview20XX.X/options/jdk.table.xml
on macOS, while Android Studio is not open fixes the issue, which no longer appears after opening Android Studio back after that.
c
That did the trick! Thanks @wasyl!!!
w
Am I missing something? The issue you pasted is Giraffe hanging, is that related to the missing classpath error?
Also, giraffe canary 2 hanging is a known issue canary 3 should be fine
c
Whoops. posted that msg+link in the wrong thread. deleting that message