A modern programming language that makes developers happier.

kotlinlang

In 2.x, we used to have <https://github.com/HedvigInsurance/android/blob/ce1d11276f91ae2fcd6c5b6074a84ff9a3911a0d/app/src/main/java/com/hedvig/app/ApplicationModule.kt#L307-L317|subscriptionConnectionParams and subscriptionTransportFactory>. In 3.x we don’t.
I’ve tried constructing my ApolloClient <https://github.com/HedvigInsurance/android/blob/apollo3-15-misc_fixes/app/src/main/java/com/hedvig/app/ApplicationModule.kt#L299-L320|without> replacing it with anything, thinking maybe the necessary headers will be added from the <https://github.com/HedvigInsurance/android/blob/ce1d11276f91ae2fcd6c5b6074a84ff9a3911a0d/app/src/main/java/com/hedvig/app/ApplicationModule.kt#L265-L267|OkHttp interceptor> instead which didn’t work. The <https://github.com/apollographql/apollo-kotlin/blob/bb8b52dacf7c57f84936f1e8082bbaf3366413da/docs/source/tutorial/11-subscriptions.mdx#L65-L71|docs >show a setup like this, but maybe this doesn’t work when there’s authentication etc on the play.
Tried instead going full out by using <https://github.com/HedvigInsurance/android/blob/acfcf67113ae84e644f6cef52655c46543e8dd34/app/src/main/java/com/hedvig/app/ApplicationModule.kt#L304-L316|subscriptionNetworkTransport> on the builder but this also brings the same issue. I feel like I am missing some big part of the puzzle here somehow.

The exception is all referencing methods that are internal to flow or the apollo library so they don’t give me a lot of ideas on where to look next :thinking_face: The message says:
`com.apollographql.apollo3.exception.SubscriptionOperationException: Operation error ChatMessage` where <https://github.com/HedvigInsurance/android/blob/ee67b6a0caffb4efe662d4c8a4a9db35ba9c3600/apollo/src/main/graphql/com/hedvig/android/owldroid/graphql/chatMessages.graphql#L7-L11|ChatMessage> is a subscription. And I don’t quite know where to go from there, hence here I am if you have any obvious thing I am missing.

You probably need a connection payload. <https://www.apollographql.com/docs/kotlin/advanced/authentication#authenticating-your-websockets|This doc> shows how.

Hmm but in the “Alternatively…” section it adds that one can do it with the `subscriptionNetworkTransport` and `addHeader` approach which I have tried as well. Is it different than using `wsProtocol` and `connectionPayload`?
Also good to note that this *may* be a good candidate to be added to the migration to 3.x docs since it’s not mentioned what one should use instead of subscriptionConnectionParams and subscriptionTransportFactory in the <https://www.apollographql.com/docs/kotlin/migration/3.0/#subscriptions|subscriptions> section.

Yes, the 2 ways don't have the same effect and the one you need depends on the backend implementation.

• `connectionPayload` will be sent along with the first message sent right after connecting (the `connection_init` message)
• `addHeaders` will be used at a lower (http) level

Ahaaa, it does seem to not crash anymore now. This was very non-obvious to me, as I am not that well-versed in these low-level details. Thank you so much Benoit!

you're welcome!  And good call about the migration guide, I'll have a look at adding this info.

Ah I just saw this, I just came here to say I opened <https://github.com/apollographql/apollo-kotlin/pull/4188|this> to help a bit. it’s a simple mention of the lack of `subscriptionConnectionParams` and a link on where to get this information. But I see you said you might look into this, if you wanted to write something more comprehensive feel free to reject the PR!

oh very nice! :pray: No worries I didn't start anything on my side :slightly_smiling_face:

I wondered about what you feel about relative references to other docs. I added `../advanced/authentication.mdx#authenticating-your-websockets` in there but doing a project-wide search I don’t see any other reference to “.mdx” so if you want a different approach I’d like to know for future reference as well :thinking_face: