Move subscription errors to status change handler

[achager]

Feature Request For manual (non DeltaSync) subscriptions created with the client.subscribe function call, subscription errors should all trigger the statusChangeHandler callback. As of release 2.10.3 with the addition of the subscription statusChangeHandler it is confusing to have errors sometimes occur in the resultHandler (i.e. on subscription startup) and sometimes on the statusChangeHandler.

Describe the solution you'd like When the subscription encounters an error that it cannot gracefully recover from and moves into an .error state, it should alert the calling code via the same callback method, preferably the statusChangeHandler.

[rohandubal]

Thanks for bringing this up @achager

I will have a discussion with the team to determine what should be our best path forward to ensure consistency. I will put some recommendations on this thread which we can discuss and implement.

Best, Rohan

[sravichandran-gd]

@rohandubal Do you have an update on this feature request? We are facing some issues with subscriptions. We would highly benefit with this feature. Thank you.

[atierian]

Thank you for opening this issue. AWS AppSync SDK for iOS entered maintenance mode in September 2023 and will receive no further updates as of September 2024.

Please use Amplify Swift going forward. For information on upgrading to Amplify Swift, refer to the Upgrade from AppSync SDK documentation.