The API GraphQL subscription behavior should continue to receive updates (or be reconnected) across IP address changes.
The device/browser IP address may change when moving between wifi or cellular networks. When this occurs, either:
The websocket should remain active and uninterrupted.
The websocket should be disconnected immediately prompting reconnection.
Describe the solution you'd like
AppSync should continue to send data to websockets across IP address changes.
Describe alternatives you've considered
The Amplify client should recognize when the AppSync subscription is broken either by watching for IP address changes or because AppSync sends error messages that will trigger the errant connection to close. In both cases the client should automatically reconnect.
Additional context
Reproduction steps:
Setup an application with an API subscription following data updates
Confirm that under normal conditions updates are received as expected
Simulate that when the device IP address changes, the websocket remains, but no longer receives updates.
Simulate IP address change by either logging in to or disconnecting from a VPN
Note that in connection states this ip address transition doesn't cause the network to be unavailable in my testing. The connection issue is that we miss Keep Alive messages following the IP address change.
Is this something that you'd be interested in working on?
[ ] 👋 I may be able to implement this feature request
Is this related to a new or existing framework?
No response
Is this related to a new or existing API?
GraphQL API
Is this related to another service?
AppSync
Describe the feature you'd like to request
The API GraphQL subscription behavior should continue to receive updates (or be reconnected) across IP address changes.
The device/browser IP address may change when moving between wifi or cellular networks. When this occurs, either:
Describe the solution you'd like
AppSync should continue to send data to websockets across IP address changes.
Describe alternatives you've considered
The Amplify client should recognize when the AppSync subscription is broken either by watching for IP address changes or because AppSync sends error messages that will trigger the errant connection to close. In both cases the client should automatically reconnect.
Additional context
Reproduction steps:
Note that in connection states this ip address transition doesn't cause the network to be unavailable in my testing. The connection issue is that we miss Keep Alive messages following the IP address change.
Is this something that you'd be interested in working on?