Hello, since apollo-android is not just for Android, I'd like it to be renamed to apollo-kotlin If you agree, would you please take 7 seconds to add a 👍🏼 on this issue, or even add a comment to weigh in? https://github.com/apollographql/apollo-android/issues/3317

Is it possible to have strict runtime validation to check: • that the

__typename

field matches the expected type name from schema • that the json response doesn’t contain unnecessary fields/objects ?

This message was deleted.

apollo 2.x.x had

clearNormalizedCache

function available on ApolloClient, how do you perform this with apollo3?

Hey folks, while running UI test cases, I wanted to mock the data coming from graphQL. Our implementation is

val response = ApolloGraphQL.getClient().query(RandomQuery()).await()

Here the response will be of data type RandomQuery.Data , which is a data class. Is it possible I can add fake data and mock the response here? I see in the generated class (RandomQuery.Data class), there is a function, which parses the data somehow

operator fun invoke(reader: ResponseReader)

Found the issue here. Looks like it was fixed in kotlin v1.5.30

I wonder if anyone has any thoughts about migrations in Apollo. We’re using the normalized cache extensively, and the app relies on some data being available immediately, even if it’s not entirely up-to-date. This all works fine as long as we don’t modify the query for that data, but once we do, we have a cache miss and reach out to the network. That’s fine, but sometimes that initial request takes time or fails, and we end up with no data at all. I’m thinking about implementing some kind of migration, where the app would be made aware of new fields added for some objects, and it would manually save some default data in the cache. That way we’d avoid a cache miss if a field was added and the device is e.g. offline. Does that make any sense?

Hi again! I just starting moving some graphql’s to it’s own module. This module will perform the request, then return the response to the

app

module. I’m getting this error. I’d rather not have to append a !! or any special null checks to this if possible. I’m using version Apollo version

2.5.9

lazy bug report: I had a query

SomefooQuery

with generated Kotlin classes. I renamed it to

SomeFooQuery

, and

compileKotlin

failed with

Redeclaration: SomeFooQuery

and

Redeclaration: SomefooQuery

errors. Seems like the lowercase file was kept and shouldn’t,

--rerun-tasks

fixed the issue

Does Apollo for multiplatform generate your queries for you? reading here: https://www.apollographql.com/docs/android/essentials/get-started-multiplatform/

Hey, i’m trying to upload a file through

SingleUploadMutation

but the

FileUpload

class does not accept a

File

as stated in docs but accepts only a

filePath: String

and if i check the

FileUpload

class there is no implementation 🤔 is the documentation not updated or am I missing something?

Morning all. Can someone share how your developers experience look like in term of schema downloading? I am interested in where do you download the schema (Apollo Studio, your servers or something else), at what point of the dev lifecycle schema is uploaded, and when and by whom it is downloaded. Anything you can share regards how useful it is greatly appreciated. I am trying to figure out what would be the smoothest process for us, taking into account that this step never existed before.

Hi all! Does anyone have any pointers on caching? I'm trying to cache & re-use the output of a query for multiple items for another query for a single item (going from a list of items to a detail screen for one). Using 3.0.0-alpha07 with a normalized cache. Simplified sample below I've changed the cache key format for an 'entry' to

Entry.<id>

using `ObjectIdGenerator`/`CacheKeyResolver` but I'm getting a cache miss for

EntryQuery

–

Object 'QUERY_ROOT' has no field named 'entry({"input":{...}})'

, before the inner

Entry

from

EntryOutput

can even be looked up in the cache (which I'd expect to succeed)

type Entry {
	id: ID!
	# ... etc
}

query EntriesQuery(...) {
	entries(input: { ... }) { # produces EntriesOutput
		nodes { # [Entry]
			id
		}
	}
}

query EntryQuery($entryId: ID!) {
	entry(input: { entryId: $entryId }) { # produces EntryOutput
		entry { # Entry
			id
		}
	} 
}

In Apollo 2, you could react to changes to the cache. What’s the best way to do this with Apollo3? Is it:

apolloClient.watch(MyQuery())

?

Hello Everyone Is there any way to handle exception handling by only one class in GraphQL like an interceptor in REST Api?

hellow everyone, Im writing an app using apollo3 (early stage of development) and the example I based myself on handles one call fine but as soon as I start calling many it ends up crashing. does anyone have a good example from github that uses apollo 3 and is able to do multiple calls to the server in parallel? Im having a hard time sifting through.

hmmmm can't find how to set retries in apollo3? 🤔

I’m in the process of converting to apollo3 (using beta 1). I added a

service

. When I build it, I get the following error:

Could not determine the dependencies of task ':app:generateServiceApolloSources'.
> Could not resolve all task dependencies for configuration ':app:apolloServiceConsumer'.
   > No variants of project :graphql-model match the consumer attributes:
       - Configuration ':graphql-model:default':
           - Incompatible because this component declares a runtime of a component and the consumer needed a usage of 'apollo-metadata' of a component
           - Other compatible attribute:
               - Doesn't say anything about com.apollographql.service (required 'service')

Does

watch

also perform a network request if it’s not already in the cache?

apolloClient.watch(BookWithAuthorName()).collect { response ->
      // This will be called every time the book or author changes
  }

Is there a way to make a query load from the cache, then perform a network request, then continue to monitor the cache for changes?

Using fragments: is there a way to put the fragment at the root at the object?

//graphql 
query myQuery {
    rootObject {
        ...On RootObjectA {
           ... myFragment
       }
    }
}

fragment myFragment on RootObjectA {
   id
   name
}

//Kotlin object gets structured like this:

rootObject.fragments.myFragment.id
// What Id like to see:

rootObject.id.  // or rootObject.fragments.id if `fragments` are required because of the casting from the ON function

Does anyone know if there's an equivalent API to

refetchQueries

(to trigger the refetch of a given query following a mutation) in 3.x? Never used this before, but I can see references to the feature searching the Github repo, which I assume are 2.x. Can't work out if there's something I've missed for 3.x

I had recently updated to 3.0.0-beta01, and today updated my dependencies to 3.0.0-beta02 and nothing compiles anymore. I must be missing something. I get a lot of things like:

ApolloRequest<GetUserQuery.Data> but Query<TypeVariable(D)> was expected

and

Unresolved reference: hasErrors

and a bunch more like this. I'll keep looking.

Ran into a strange networking issue. We have our network transport set up as follows:

val networkTransport = HttpNetworkTransport(
        connectTimeoutMillis = 5_000,
        readTimeoutMillis = 60_000,
        serverUrl = "${config.serverUrl}/graphql",
        interceptors = listOf(
            BearerTokenInterceptor(tokenProvider = object :
                com.apollographql.apollo3.network.http.TokenProvider {
                override suspend fun currentToken(): String {
                    return config.tokenProvider.currentToken()
                }

                override suspend fun refreshToken(previousToken: String): String {
                    return config.tokenProvider.refreshToken(previousToken)
                }
            })
        )
    )

Specifically note the connect timeout, which differs from the default 60 seconds. This used to work on Android and iOS until migrating to the 3.0.0beta builds. What we discovered today was a particular call, which we know takes a bit over 30 seconds, was failing on iOS, however most of the other mutations we have succeeded. So we tried changing the connectTimeout to 60_000 instead, and that succeeded. I haven't verified, but suspect, this means that the iOS networking call might be using connect timeout instead of read timeout, or something like that. Just thought I'd report it here. Can also report on the github if preferred.

Getting a lot of errors like this from:

okhttp3.OkHttpClient - A connection to <https://example.com/> was leaked. Did you forget to close a response body?

I'm using 2.5.9, and apollo-runtime is the only user of okhttp3, except that I have

com.squareup.okhttp3:logging-interceptor

enabled. Is there anything in particular I should look for in my code that might be causing this?

We had a strange, transient (I have no evidence of this), issue with a mutation yesterday that seemed to be cached and had overrun the maximum field length of the cache. We cleared the app data, and the issue went away. I read the documentation in the code and it says that mutations use a fetch policy of

NETWORK_ONLY

, so it seems strange that the sqlite cache would be used at all for any of this. I'll update to the latest beta and see if we see it again.

Hey guys. Starting to work with apollo3 and KMM. I'm wondering why this is an assertion during execution

assertMainThreadOnNative()

if I'm trying to execute a query. Why am I forced to do it on the main thread?

Hi everyone 👋 . We just released `3.0.0-rc01`🎉 : • Changelog • Documentation • Migration Guide If everything goes well, we're planning to go stable next week 🤞. In a nutshell, Apollo Android 3 brings: • a 100% Kotlin codebase, using coroutines APIs and KMP support • a new (optional) codegen that maps the Json response 1:1 and models fragments as interfaces • declarative cache with

@typePolicy

• client-side non-nullability with

@nonnull

• a test builder DSL • SQLite batching and many more performance improvements • AST and lower level primitives to manipulate your queries If you haven't already, now is a good time to look at it and offer feedback. Changing things will be way harder once all the APIs are all frozen like a Kotlin native StableRef using the old memory model 🙃 . Feel free to reach out here or on Github!

👋 I want to manually modify Apollo cache state. 2.x exposed

ApolloStore#writeAndPublish

which required query and query data only. 3.x exposes

ApolloStore#writeOperation

but in my scenario it also requires passing

customScalarAdapters: CustomScalarAdapters

(to properly handle passed data object) Is there any way to access

customScalarAdapters

set previously on

ApolloClient

instance?

Is there no more .logger function on the builder in 3.0? Is there an alternative or should it be done manually somehow? I didn’t see this being mentioned in the migration logs, a bit lost here.