Skip to content

Subscription not working: connection_ack sent with null ID #168

@s2quake

Description

@s2quake

I built a server using GraphQL.AspNet and a client using graphql-platform, but subscriptions do not work.

The issue seems to be caused by the ConnectionAck message being sent like this:

{"id":null,"type":"connection_ack"}

I opened PR #8224 in the graphql-platform repository, but the maintainer pointed out that according to the graphql-ws protocol specification, the id field must not be null in a connection_ack message.

I'm not sure which behavior is correct or which side (server or client) should be fixed, so I'm opening this issue for clarification.

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions