Do not call success callbackon Android when Activity is signaled to be destroyed.

[wspresto]

Success callback is not called on Android when Activity is signaled to be destroyed. Instead, an error message (ABORTED) is signaled to client. This helps to clear up the ambiguity during a common android activity life cycle event (onDestroy), because previously the client code was unable to discern the reason for a successful callback execution. The reasons for a success callback could possibly be for activity termination OR playback naturally coming to an end (EOF reached).

[wspresto]

Will this ever make it in?

[wspresto]

Still? Can you at least provide an adjudication on this?