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

Fix channel not shutdown properly issue. #119

Open
avikumar15 opened this issue Jan 16, 2020 · 2 comments
Open

Fix channel not shutdown properly issue. #119

avikumar15 opened this issue Jan 16, 2020 · 2 comments

Comments

@avikumar15
Copy link
Member

After switching some fragments, the logcat prints the following error:

  • ~ * ~ * ~ Channel {0} was not shutdown properly!!! ~ * ~ * ~ *
    Make sure to call shutdown()/shutdownNow() and wait until awaitTermination() returns true.
    java.lang.RuntimeException: ManagedChannel allocation site
@Harsh2098
Copy link
Collaborator

Something related to Dagger scopes, the channel isn't shared between fragments.

@Harsh2098 Harsh2098 self-assigned this Jan 29, 2020
@delta delta locked as too heated and limited conversation to collaborators Oct 27, 2020
@ranaaditya
Copy link
Contributor

After switching some fragments, the logcat prints the following error:

* ~ * ~ * ~ Channel {0} was not shutdown properly!!! ~ * ~ * ~ *
  Make sure to call shutdown()/shutdownNow() and wait until awaitTermination() returns true.
  java.lang.RuntimeException: ManagedChannel allocation site

We are not maintaining the Channel's lifecycle according to the lifecycle of Fragment/Activity that's why its throwing these errors in logcat !

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

No branches or pull requests

3 participants