You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 14, 2018. It is now read-only.
We're using robospice-spring-android version 1.4.11 on a project. We're seeing that we sometimes get a network callback on a detached Fragment, which leads to a NullPointerException in the code. As suggested in the Wiki, we have tied the SpiceManger to the Fragment lifecycle and not the Activity lifecycle.
This problem is very hard to reproduce and happens very rarely. Our hunch is that it may be due to a race condition in the framework, but we haven't been able to narrow it down.
As a workaround, we are checking for Fragment.isAdded() in our callbacks.
Has anyone faced a similar issue?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
We're using robospice-spring-android version 1.4.11 on a project. We're seeing that we sometimes get a network callback on a detached Fragment, which leads to a
NullPointerException
in the code. As suggested in the Wiki, we have tied the SpiceManger to the Fragment lifecycle and not the Activity lifecycle.This problem is very hard to reproduce and happens very rarely. Our hunch is that it may be due to a race condition in the framework, but we haven't been able to narrow it down.
As a workaround, we are checking for
Fragment.isAdded()
in our callbacks.Has anyone faced a similar issue?
The text was updated successfully, but these errors were encountered: