When queuing up multiple messages to send and waiting for them to complete, when an exception occurs within one (or more) notifications, there's currently no way to know which one failed as PushServiceClientException only exposes the statuscode & reasonphrase. Would like to see PushSubscription & Response Headers added to exception.
The need for this stems from being able to clean-up subscriptions in the datastore when they're no longer registered.
Fortunately, the subscription is available where this would be needed and the full response is already in the method that generates the exception.
When queuing up multiple messages to send and waiting for them to complete, when an exception occurs within one (or more) notifications, there's currently no way to know which one failed as PushServiceClientException only exposes the statuscode & reasonphrase. Would like to see PushSubscription & Response Headers added to exception.
The need for this stems from being able to clean-up subscriptions in the datastore when they're no longer registered.
Fortunately, the subscription is available where this would be needed and the full response is already in the method that generates the exception.
Thank you!