IssueTracker

We'll track fixing specifically DialogFragment in this issue.

This has been fixed internally and will be released as part of the Fragment 1.3.1 version.

You can verify this by following the snapshot instructions with build id 7166224 and switching your fragment dependency to 1.4.0-SNAPSHOT.

With this bug essentially meaning that DialogFragments cannot be used with Compose, would it be possible to please backport this fix into the Fragment 1.3.0 version?

Re #5 - as per comment#4, this will be made available in Fragment 1.3.1.

The problem is when 2 fragments try setResultListener with one same result key(

As stated in the documentation "You can have only a single listener and result for a given key."

The Fragment result listeners are not stored in the Fragment, it is actually stored in the FragmentManager. So adding another listener, with the same key for two Fragments with the same FragmentManager will overwrite the first listener.

        LifecycleEventObserver observer = new LifecycleEventObserver() {
                if (event == Lifecycle.Event.ON_DESTROY) {
                    lifecycle.removeObserver(this);    // only remove observer when onDestroy
                    mResultListeners.remove(requestKey);
                }
            }
        };
        lifecycle.addObserver(observer);

I think it would be better remove observer right after the callback is fired, sometimes we don't want the observer keep listening. In that way we could wrap the whole task in one block (like coroutine style), more flexible.

Re #9 - you can certainly clear out your FragmentResultListener after you receive a result if that's the behavior you want for your business logic. The clean up mentioned in your comment is only to prevent memory leaks and not for business logic purposes.