Crash "FragmentContainerView must be within a FragmentActivity to be instantiated from XML" in app without activity [172266337]

Fixed

Bug

Status Update

No update yet.

Description

pa...@gmail.com

created issue #1

Nov 3, 2020 12:28PM

Component used: Fragment Version used: 1.3.0-beta01

With lib Fragment version 1.2 it is now recommended to use FragmentContainerView instead FrameLayout but that requires FragmentActivity.

Not sure why this requirement was introduced? In our use case user can use app on phone or mirror app to remote device with means DisplayManager.createVirtualDisplay . In both cases we use same stack of fragments, there is no need to run activity in second flow.

Can we bring this functionality back?

Comments

il...@google.com <il...@google.com> #2Nov 3, 2020 07:05PM

Assigned to jb...@google.com.

I change to fragment1.3.0 and navigation component 2.3.3, the popEnterAnim works fine. (I find the solution from the

https://issuetracker.google.com/issues/182195688 example project).

pa...@gmail.com <pa...@gmail.com> #3Nov 3, 2020 07:25PM

Please include a sample project that reproduces your issue.

As per the Fragment 1.3.2 release notes, it is expected that when you navigate(), the enter and exit animations run.

ap...@google.com <ap...@google.com> #4Nov 20, 2020 10:04PM

Thanks, here it's the project and video.

jb...@google.com <jb...@google.com> #5Nov 23, 2020 08:12PM

Marked as fixed.

I am also facing same issue exit animations does not work even if i set it from navigation graph and using Direction Classes

Issue 172266337

Description

Issue summary

Comments

il...@google.com <il...@google.com> #2Nov 3, 2020 07:05PM

pa...@gmail.com <pa...@gmail.com> #3Nov 3, 2020 07:25PM

ap...@google.com <ap...@google.com> #4Nov 20, 2020 10:04PM

jb...@google.com <jb...@google.com> #5Nov 23, 2020 08:12PM

Add comment

Issue metadata