Now that all the entries looks correct I'm trying to use apollo as the source of truth. So I hook up a watcher :

fun workOrder(id: String): Flow<Pair<WorkOrderInfo, List<FetchWorkOrderQuery.ValidFieldsetOption>>> {
        return apolloClient.query(FetchWorkOrderQuery(id = id))
            .fetchPolicy(FetchPolicy.CacheFirst)
            .watch()
            .map {
            ...
            }
    }

And the Have A mutation with an optmistic cache:

apolloClient.mutation(UpdateTaskComponentsMutation(input = newComponents))
            .doNotStore(false)
            .optimisticUpdates(
                UpdateTaskComponentsMutation.Data(
                    UpdateTaskComponentsMutation.UpdateTaskComponents(
                        listOf(
                            UpdateTaskComponentsMutation.Component(
                                __typename = newComponent.componentInfo.__typename,
                                componentInfo = newComponent.componentInfo,
                                id = newComponent.componentInfo.id
                            )
                        )
                    )
                )
            )
            .execute()

This seems to be writing in the cache alright, ( If I re enter the screen I can see the new value) But for some reason the watch is not emitting?

https://www.apollographql.com/docs/kotlin/caching/query-watchers Could not fin much more here, im goign over video sin youtube to see if I find something

Also worth trying to publishing one of the cache keys manually to see if it triggers the watcher (

apolloClient.apolloStore.publish(setOf("Component:42"))

)

watch()

also takes 2 parameters (I'm assuming you're using v3, right?). You can try setting them to true to make the flow throw on cache misses

thanks!

Ok interestingly enough. After some debug ( thanks for pointing into the right place). It seems I was adding way to many watched keys. I stoped watching one of the flows and now works. Maybe the huge amount was causing some crash that was swallowed

What's interesting is that the other flow you were watching is not related to the 1st one?

What's interesting is that the other flow you were watching is not related to the 1st one?

But they all add watch keys to the pool right?

watchedKeys

here is local to one query

cheers!