Fixed
Status Update
No update yet.
Comments
il...@google.com
Can you please provide some more information? I assume this stacktrace is from an exception, but I don't know what type of exception it is or which version of Android is involved.
Can you also give details on how you got this to happen and how often it happens? Do you have a sample project that causes this to occur?
Can you also give details on how you got this to happen and how often it happens? Do you have a sample project that causes this to occur?
il...@google.com
ap...@google.com
Sorry for not making it too clear.
The Exception it's throwing is an IllegalArgumentException in android.net.ConnectivityManager in unregisterNetworkCallback (Invalid NetworkCallback)
This is happening in our production app (after we introduced workmanager) and it's been happening for some time now.
It's happening only in Nvidia Shield Tablet and Nvidia Shield Tablet K1. We have around 200 crashes per day.
The Exception it's throwing is an IllegalArgumentException in android.net.ConnectivityManager in unregisterNetworkCallback (Invalid NetworkCallback)
This is happening in our production app (after we introduced workmanager) and it's been happening for some time now.
It's happening only in Nvidia Shield Tablet and Nvidia Shield Tablet K1. We have around 200 crashes per day.
Description
Component used: Fragment Version used: 1.3.0-alpha06
When using
setReorderingAllowed(true)(such as when using the Navigation Architecture Component), doing areplace()will cause the new fragment to go throughonCreateView(),onViewCreated()and potentially up throughonStart()andonResume()before the previous fragment is stopped.This means that any values that are set on a shared view model (i.e., when
Ideally, the previous fragment should be stopped (but specifically not have its view destroyed) prior to the new fragment moving up through lifecycle methods.