Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

wspresto
Copy link

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).

…en onDestroyed(..) is invoked by Android OS. Providing parameter in destroy method to allow for silent player destruction. Player does not broadcast state change when handler is destroyed. Player emits media aborted error when handler is destroyed.
@janpio janpio changed the title Success callback is not called on Android when Activity is signaled to be destroyed. Do not call success callbackon Android when Activity is signaled to be destroyed. Nov 19, 2018
@wspresto
Copy link
Author

Will this ever make it in?

@wspresto
Copy link
Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants