Has anyone here ever made a Subscription work on iOS under Kotlin Native willing to share an example of how they are doing it? I've time boxed myself to figure this out this morning, and I've failed. So, hoping someone else has done this. Thanks in advance.

Is there a way to send multiple mutations in one request? I'm not seeing any way to specify a list of mutations in the client API.

I might be just missing something but I don't see a way to log network traffic with Apollo multiplatform. It's pretty easy with access to OkHttp interceptor but I don't think I am able to do that from common code.

Is there some built-in or just an easy way to track queries that got

PERSISTED_QUERY_NOT_FOUND

error? Just something for logging purposes

Hi, I wanted to understand how apollo GQL plugin works for android and iOS. Do they share the same codebase for generating the platform specific code? I wanted to build something which generate the code for both the platform at compile time. Any leads would be appreciated. Is there anyway to achieve the same thing by sharing the common codebase?

Hi, I need to add a JWT header to my GraphQL subscription - does anyone know how to do this with apollo-android? (and somehow support refreshing jwts as well)

Today’s the day I'm going to make another attempt to get a GraphQL subscription working in iOS. Wish me luck. KMM memory model woes.

👋 I’m looking at 2.5.8 release, and query batching looks great, pretty excited to check it out! While looking at it, I recalled one similar optimization: attaching new queries to ones that are still running. For example I query

Foo(a, b)

and it will make network request that finishes after ~500ms. ~200ms from the first query I make second, same

Foo(a, b)

query, so the first one is still running. Would it make sense for Apollo to merge the same requests internally, and if a network request is already running — just attach the new observer to the existing one and share the result? Similarly, everything related to observing the cache could be shared as well. This is something that could be done on the app side, but seems like a useful optimisation that could be part of Apollo. Any thoughts on this?

If Application errors exist i.e 

response.errors

will the resulting response (query) be cached? Any good reading material or resources on this topic?

Is there any benefit to using

prefetch

if we’re already observing the query we want to prefetch? Will we avoid some parsing, for example? Context: we’re trying to have a separation between observing data from cache and refreshing it. Observers will do:

val observer = apolloClient.query(operation).toBuilder()
    .responseFetcher(ApolloResponseFetchers.CACHE_ONLY)
    .build()
    .toFlow()

and I wonder if there’s preferred refreshing method. One is prefetch:

fun refresh() = apolloClient.prefetch(operation).await()

another is a

NETWORK_ONLY

request and awaiting first response:

fun refresh() = apolloClient.query(operation).toBuilder()
    .responseFetcher(ApolloResponseFetchers.NETWORK_ONLY)
    .build()
    .toFlow()
    .first()

I also see

ApolloQueryWatcher#refetch

, but I don’t think it’ll work for us because it doesn’t propagate errors.

Prefetch

has some optimisations mentioned in the docs, are they relevant if we have another query observing the cache?

Is there any way to disable the

__UNKNOWN

elements for enums? They are annoying because they basically break exhaustive whens. I'd rather have the compiler tell me a new enum was added and it needs to be handled rather than dealing with

__UNKNOWN

explicitly everywhere.

Do you have any idea why the composite test build tries to fetch the Apollo JS library from npm? Of course it couldn't find it.

Hi @mbonnin sorry to bother you on weekend. Any idea to solve this problem? I cannot write any code today since this build failure 😂. https://github.com/apollographql/apollo-android/issues/3210

[SOLVED] I get the following error when running Jacoco and it crashes when analyzing an Apollo generated class:

Caused by: java.io.IOException: Error while analyzing DeleteVisitsByUuidMutation$Data.class.

I am using Jacoco 0.8.7 and Apollo 2.5.9

Hello Everyone is there any blog or sample for Apollo graphql for Multiplatfrom POC I working POC Sample using Apollo Client

Hi everyone 👋 ! Apollo Android version

3.0.0-alpha01

is available on Maven Central! That's a pretty significant release that unifies

apollo-runtime

and

apollo-runtime-kotlin

(and most importantly will make the Github bar 100% #A97BFF !!). It should make it way easier to work with multiplatform code, including caching. It also makes reading the SQL cache wayyyyyyyyyy faster, has a new codegen mode that generates fragments as interfaces,

@nonnull

directives and more... Full details: • Changelog: https://github.com/apollographql/apollo-android/releases/tag/v3.0.0-alpha01 • Migration guide: https://www.apollographql.com/docs/android/v3/migration/3.0/ Obviously it's still alpha so please report any weird behaviour or things you'd like to change, feedback is very welcome!

hi all! I've been playing around with an apollo client to test a graphql api, wich I really like. I use a ktor server and

sessions

to allow authentication with cookies, but I'm not sure how to configure the apollo client to allow cookies. Any suggestions are helpful, thank you! 🙏🏻 My code looks like this:

val url = "....

                   val okHttp = OkHttpClient
                        .Builder()
                        .build()

                   val apolloClient = ApolloClient
                        .builder()
                        .serverUrl(url)
                        .okHttpClient(okHttp)
                        .build()

based on the documentation found here, I should be able to add this to my gradle file:

apollo {
    service("foo") {
        generateAsInternal.set(true)
        schemaFile.set(file("src/commonMain/graphql/com/example/shared/graphql/schema.graphqls"))

        registry {
            graph.set("example-123")
            graphVariant.set("variant")
            key.set(".....")
        }
    }
}

and then just run

./gradlew downloadApolloSchema

but I’m being met with the following error

* What went wrong:
Execution failed for task ':shared:downloadApolloSchema'.
> ApolloGraphQL: no schema property

I assume I’m missing something simple?

Does anyone know what could be causing this issue? I’m using fragments.

Something changed between v3.0.0-dev14 and v3.0.0-alpha01 that is now causing one of my mutations to never return. I'm looking into it more but thought I would post this in case it rings a bell with anybody involved in making those changes.

Is there any plan to rename "Apollo Android" to just "Apollo Client", now that it supports multiplatform/ JVM as well? Its a bit confusing, and IMO hurts discoverability, to refer to it as "Apollo Android" when its perfectly usable without Android.

Is there an ApolloInterceptor example out there that logs requests / responses + request body?

Hello, Im investigating

Apollo3

on Android

Does the new query batching support also handle batching mutations? I have a streaming pipeline that does mutations, and I'm looking to batch up those mutations and send them to the server in one network call. Aliases do not work for this use case: I don't know in advance how many mutations I have.

Is there a good way to have the client emit a

sealed class

for the response? I’d like to emit various states such as

loading

,

failure

, and

success

but I don’t want to have to implement this on every call, I’d rather just do it in one spot 😄

Hi, Im running through the Apollo tutorial and having trouble generating the subscrition data model

Hi all! I've upgraded to use

apollo3

, unfortunatelly I can't manage to configure it such that the mutations/queries are not generated at each run. I've set this:

generateKotlinModels.set(false)

, but seems to have no effect. Not sure if there's anything else I could do, is there a way to disable generating everything at each run? 🙏

Question 1: I’m starting to receive this error more and more frequently, I wiped out my cache yesterday and ran into tons of gradle issues after that, then once i fixed those issues I didn’t run into it again until just now:

java.lang.NoSuchFieldError: No static field ISO8601DATETIME of type Lcom/xxx/android/type/CustomType; in class Lcom/xxx/android/type/CustomType; or its superclasses (declaration of 'com.xxx.android.type.CustomType' appears in /data/data/com.xxx.android/code_cache/.overlay/base.apk/classes18.dex)

Do you think it’s related to this? https://github.com/apollographql/apollo-android/issues/2043

------ Question 2: I just joined a team and a lot of apollo calls are scattered around the project, there’s not really much organization to it at all. This also is the way with iOS. Would it be a terrible idea to create a new module, include Apollo3, while still leaving Apollo2 in the main app module? Then I could slowly migrate to the new Apollo3 and have cleaner architecture and allow iOS to consume the same calls?