You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I'm not able to receive any updates from subscriptions when using arguments in my application. I am able to reproduce the issue using the chat sample app while only using the AWS console so I'll leave any other setup out here.
Maybe I'm wrong, but at first sight it looks you should include your argument 'conversationId' in list of mutation fields.
Responses are filtered out by the argument if you specify them, and your response from mutation must contain that conversationId if you want to be received by subscription.
Subscription response will just reflect what's sent from the mutation.
Maybe I'm wrong, but at first sight it looks you should include your argument 'conversationId' in list of mutation fields.
Responses are filtered out by the argument if you specify them, and your response from mutation must contain that conversationId if you want to be received by subscription.
Subscription response will just reflect what's sent from the mutation.
Hmmm, that fixed it. This seems very confusing to me my assumption was that it is filtered by the argument I send in the mutation, not the one that I query for. Thanks for clearing this up.
Describe the bug
I'm not able to receive any updates from subscriptions when using arguments in my application. I am able to reproduce the issue using the chat sample app while only using the AWS console so I'll leave any other setup out here.
To Reproduce
Expected behavior
The subscription receives the results of the
createMessage
mutation.Additional context
If I remove the argument from the subscription it works as expected
The text was updated successfully, but these errors were encountered: