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

Modules become unresponsive to lifecycle when any activity is destroyed #98

Open
alechill opened this issue May 29, 2019 · 0 comments
Open

Comments

@alechill
Copy link

If an activity that does not own the drawer gets destroyed, DebugDrawerLifecycleCallbacks onActivityDestroyed(Activity activity) de-registers the lifecycle hooks for the drawer and its modules

This manifests in the drawer modules not having their onStart/onStop/onPause/onResume/onOpened/onClosed handler methods being called any longer, even though the drawer is still accessible

All other DebugDrawerLifecycleCallbacks methods check first if the activity that invoked the lifecycle is the owner of the drawer before delegating, this needs to happen here too

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

No branches or pull requests

1 participant