-
Notifications
You must be signed in to change notification settings - Fork 819
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Amplify Mock AWSAppSyncRealTimeProvider Connection error #2935
Comments
@riacoding Mock does not yet support the new WebSocket based subscriptions, only MQTT and the code you're trying to run using the new AmplifyJS library is leveraging the new WebSocket based subscriptions, hence creating this error for you. |
@attilah is there a roadmap to have this feature implemented? I understand the issue but it seems more of a regression as it was working in 1.2.4. I have been looking at the repo ,Am I right to assume that the mock would need to implement a pure WS server instead of MQTT to handle the new AWSAppSyncRealtimeProvider? |
@riacoding - any success on this? |
They said it’s in the pipeline for getting fixed but there is no timeline
as of yet
…On Wed, Feb 19, 2020 at 10:53 AM narayanncube ***@***.***> wrote:
@riacoding <https://github.com/riacoding> - any success on this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2935?email_source=notifications&email_token=AACZHNSYFVXF7D4RHLINN53RDV537A5CNFSM4JWMMZF2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMJA5NQ#issuecomment-588385974>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACZHNX3W3ICTVLNMF7BOVDRDV537ANCNFSM4JWMMZFQ>
.
|
Ok Thanks for replying
|
any update on this @riacoding |
Not at this time. Last I heard it was on the backlog but with no priority.
Hopefully the more awareness the quicker the fix
…On Sun, Mar 15, 2020 at 11:55 AM Camin McCluskey ***@***.***> wrote:
any update on this @riacoding <https://github.com/riacoding>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2935 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACZHNX5RHDOC6QPNJFLJLLRHUQBFANCNFSM4JWMMZFQ>
.
|
Facing this issue as well still. |
we are at the second wave of god damn covid! |
+1 for this fix |
Unsure if this is the same original issue above, but I filed this bug regarding Mock AppSync Subscriptions. |
Hey y'all as noted in @mgarabedian 's comment this item is currently being tracked on aws-amplify/amplify-category-api#122. Closing in favor of tracking 9621. As a workaround we can use a proxy or frontend app config to rewrite |
Describe the bug
Create a fresh react project and add amplify to it with an API. On running
amplify mock api
the graphql subscriptions are not working as expected with the AWSAppSyncRealTimeProvider having a connection failed exception after timeout.Amplify CLI Version
Amplify/Cli@4.5.0
To Reproduce
Following demo from aws blog post by Nikhil Dabhade
https://aws.amazon.com/blogs/mobile/amplify-framework-local-mocking/
replace App.js with code below
amplify mock api
npm start
Expected behavior
From the http://localhost:20002/ local endpoint using graphiql to create a mutation create a todo item. This would then be automatically updated on the http://localhost:3000/ endpoint via the graphql subscription.
Screenshots
Desktop (please complete the following information):
Additional context
The mutations are being persisted to the local database and the changes can be viewed by refreshing the page, however, the websocket is not updating in realtime.
The text was updated successfully, but these errors were encountered: