Deprecate getFragmentManager in Fragment [140574496]

Fixed

Feature Request

Status Update

No update yet.

Description

jb...@google.com

created issue #1

Sep 5, 2019 08:43PM

GetFragmentManager() returns the FragmentManager that the Fragment is added to, not the childFragmentManager, which is the one that it owns. We should deprecate this, and replace it with getParentFragmentManager() to make it clear what is actually being returned by this API.

Comments

ap...@google.com <ap...@google.com> #2Sep 6, 2019 11:39PM

This was fixed in

https://issuetracker.google.com/issues/134673465

which is part of Fragments 1.2.0-alpha01:

https://developer.android.com/jetpack/androidx/releases/fragment#1.2.0-alpha01

Can you upgrade Fragments and see if this fixes your issue?

jb...@google.com <jb...@google.com> #3Sep 7, 2019 12:03AM

Marked as fixed.

After update to Fragments 1.2.0-alpha01, it seems the same exception still happens (Also tried update appcompat:1.1.0-rc01)
The latest example project was attached

Issue 140574496

Description

Issue summary

Comments

ap...@google.com <ap...@google.com> #2Sep 6, 2019 11:39PM

jb...@google.com <jb...@google.com> #3Sep 7, 2019 12:03AM

Add comment

Issue metadata