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
{{ message }}
This repository has been archived by the owner on Apr 10, 2020. It is now read-only.
Updated schema.graphql to reflect recent pull requests made to the source code's schema.graphql -- the subscription error handshake is gone and thus debugging the app isn't producing any errors.
However, when loading a conversation, what's published shows from the current user, yet doesn't display for the subscriber. Additionally, if the subscriber replies with its own pub, that message/conversation loads in one frame, then rerenders as if the received conversation did not exist.
Addendum: Running on Node 10.x, Node 8.x seems to be deprecated and will deny amplify push without updating Amplify settings to Node 10.x. Not sure if this part of the issue in creating inconsistencies with chat features.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Updated schema.graphql to reflect recent pull requests made to the source code's schema.graphql -- the subscription error handshake is gone and thus debugging the app isn't producing any errors.
However, when loading a conversation, what's published shows from the current user, yet doesn't display for the subscriber. Additionally, if the subscriber replies with its own pub, that message/conversation loads in one frame, then rerenders as if the received conversation did not exist.
Addendum: Running on Node 10.x, Node 8.x seems to be deprecated and will deny amplify push without updating Amplify settings to Node 10.x. Not sure if this part of the issue in creating inconsistencies with chat features.
The text was updated successfully, but these errors were encountered: