Changing the setFragmentResultListener() code to be in line with what we use in MessageViewFragment.
Since we have no idea where the navigation/lifecycle-related crashes reported via Google Play come from, I'm going through recent changes that touched navigation or lifecycle observers. This usage of setFragmentResultListener() is new and could be related to the problem. But that's just a guess. This change is unlikely to make things worse.
Changing the
setFragmentResultListener()code to be in line with what we use inMessageViewFragment.Since we have no idea where the navigation/lifecycle-related crashes reported via Google Play come from, I'm going through recent changes that touched navigation or lifecycle observers. This usage of
setFragmentResultListener()is new and could be related to the problem. But that's just a guess. This change is unlikely to make things worse.