Hello! I am having a small issue with `checkServic...

# apollo-kotlin

[Eduard Boloș]

Hello! I am having a small issue with checkServiceApolloDuplicates. I am getting this build error:

> duplicate Type 'ResolverKey(kind=OperationVariablesAdapter, id=CancelAgentTransactionMutation)' generated in modules: agent,field
  Use 'alwaysGenerateTypesMatching' in a parent module to generate the type only once

In the parent module I already added apollo { alwaysGenerateTypesMatching.set(setOf("CancelAgentTransactionMutation", "other types here")) }, but the error is still there 😄 Any ideas what might be going on?

[Eduard Boloș]

Just to clarify, I was getting similar errors for other types as well, which after adding to alwaysGenerateTypesMatching disappeared, but this one for CancelAgentTransactionMutation doesn't want to go away 😄

[bod]

hmmm this reminds me of a similar issue in the past where cleaning the build resolved it 😅 Have you already tried that by any chance?

[Eduard Boloș]

This also happens on clean builds on the CI :)

[bod]

all right it was worth trying 🙂

[bod]

let me see if I can repro on a basic multi module project

[bod]

apparently not 😅 . Do you have any queries/mutations/subscriptions in your schema module?

[Eduard Boloș]

I'll try to come up with a small repro project tomorrow. Thanks for looking into it meanwhile :)

[bod]

Repro project would definitely help 🙏

[bod]

Hey could it be that you have the mutation CancelAgentTransactionMutation defined in several modules? 🤔 (thanks @mbonnin for the idea! 🙂)

[Eduard Boloș]

ah, it seems like that is the case 😄 should I rename one of them? (they have different queries, I can't just pull one of them in the parent module), or is there any other solution? 😄

[bod]

yeah having different names is certainly the best thing to do

[mbonnin]

Yea, we have a requirements that names are unique and a nice check for this but the check is only for a single module

[mbonnin]

We should make that error message a bit better

[mbonnin]

In theory, we could allow same operation name with different packages in different modules but that's not a great idea for observability. I.e. someone logging the operations in your backend will most likely be confused

[Eduard Boloș]

yeah, I can see that happening in general. for us in particular, field and agent are separate apps, which include their own client name headers in the requests, so differentiating is easy 🙂

[Eduard Boloș]

just to confirm, renaming fixed the issue. thanks again for your help!

[mbonnin]

That rings a bell. It's this issue: https://github.com/apollographql/apollo-kotlin/pull/4402

[mbonnin]

Do you mind trying with the 3.6.1-SNAPSHOT ? If everything looks good, we'll make a patch release

[Eduard Boloș]

yeah, it's all good with the snapshot version 🙂

[mbonnin]

Thanks for confirming, launching the build

[mbonnin]

It's rolling out to maven central, it should typically be live in ~20min

[Eduard Boloș]

thanks for such a short turnaround time! ❤️

[mbonnin]

Sure thing! We ended up branching for the release (cause we have a bunch of things in flux in main at the moment) but it should have the fix from the SNAPSHOTs, let us know otherwise!