Getting an Error for Invalid Subscription Requests
See original GitHub issueI’m currently working on integrating GraphQL subscriptions in Ballerina language to a GraphiQL web based client. It uses websockets for subscriptions and works fine with valid subscription requests. But for invalid subscription requests, an error occurs like this.
The GraphiQL client receives this websocket payload.
{"type":"error", "id":"b2dd2712-1ac5-48fa-9f25-8b88d3d80bf0", "payload":{"errors":[{"message":"Cannot query field \"messag\" on type \"MsgType\".", "locations":[{"line":4, "column":5}]}]}}
Issue Analytics
- State:
- Created a year ago
- Comments:8
Top Results From Across the Web
How to fix invalid subscription - Red Hat Customer Portal
Try to "unregister, clean and remove" subscription and register it back as explained before.
Read more >signatureUnsubscribe error: Invalid subscription id. #1100
Hi Guys, I am getting the same error. I have 10k assets. Rejecting for timeout... Timeout Error caught { timeout: true } Error...
Read more >Error code: 614 invalid subscription - Marketing Nation - Marketo
Error code: 614 invalid subscription. My web application has started receiving 614 error which is not listed in the error code page.
Read more >Invalid Subscription Key for python code but same key is ...
But I am getting the following error when using the python code. {"statusCode": 401, "message": "Access denied due to invalid subscription ...
Read more >Receiving unauthorized errors (401) while invoking APIs - Azure
To get access to the API, developers must first subscribe to a product. · Regarding error Access denied due to invalid subscription key....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks for reporting @Nuvindu! I thought this would be a regression with the recent refactorings we did, but seems like this has been an issue even before that. I opened a PR that would fix this.
This should now be fixed in
graphiql@1.11.1