FragmentScenario requires modification to non-test code to work [128612536]

Fixed

Feature Request

Status Update

No update yet.

Description

hu...@google.com

created issue #1

Mar 14, 2019 06:09PM

FragmentScenario requires modification to non-test code to work. This is not the ideal as the setup is complicated and leads to counter-intuitive behavior such as

b/122321150

. Ideally, FragmentScenario should work by just having dependency in test APK and don't require modification in the target APK.

The reason of this limitation is that activities defined in test APK run in different process from the target process (unless you set sharedUserId). FragmentScenario uses EmptyFragmentActivity as the host Activity and it is defined in the library's manifest. In order to start EmptyFragmentActivity in the target app process, the manifest needs to be merged into the target APK.

This thread is to track the progress of removing this limitation.

Comments

hu...@google.com <hu...@google.com> Mar 14, 2019 07:42PM

Assigned to hu...@google.com.

[Deleted User] <[Deleted User]> #2Mar 17, 2019 05:22PM

Please include a sample project that reproduces your issue.

do...@google.com <do...@google.com> #3Mar 9, 2020 03:23PM

Here is the sample project.

Steps to reproduce:
1. Press on "Search" icon;
2. Write something;
3. Search this text, keyboard will be dismissed;
4. Tap on "Dialog" button;
5. Dissmiss dialog;

With the new 1.5.0 fragment library version text will be cleared in the search box after dismissing dialog.
In the version 1.4.1 and lower text in the search is not clearing and this is correct behaviour.

Please suggest some workarounds or how to fix this issue?

sa...@peilicke.de <sa...@peilicke.de> #4Apr 14, 2020 06:31AM

Hello, have you checked sample project? I hope it will help find the issue.

ya...@lightricks.com <ya...@lightricks.com> #5Jun 30, 2020 07:37AM

@3
I've described a weird workaround that I got, here:

https://issuetracker.google.com/issues/244854449#comment3
Sample:

https://issuetracker.google.com/issues/244854449#comment4

It probably has bugs of its own that I didn't think of.
Google please fix this.

hu...@google.com <hu...@google.com> Jun 30, 2020 06:32PM

Status: New

an...@gmail.com <an...@gmail.com> #6Aug 17, 2020 05:49PM

Hello, any update please?

np...@platformscience.com <np...@platformscience.com> #7Oct 21, 2020 07:15PM

Hello I raised similar issue with this ticket https://issuetracker.google.com/issues/249247706

This makes the SearchView unusable/broken when fragments are changed (i.e base on searchView input query)

What can we do to fix this problem? What is the progress of work on solving this problem?

st...@gmail.com <st...@gmail.com> #8Nov 17, 2020 06:34PM

@7 Check @5 for a workaround.

do...@gmail.com <do...@gmail.com> #9Dec 31, 2020 05:24PM

Hi, i am also facing this issue after we dismiss a DialogFragment, the callback comes in the onPrepareOptionsMenu(), which is causing the issues for me.
Any idea on when it will be fixed?

al...@gmail.com <al...@gmail.com> #10Feb 18, 2021 04:51AM

Hello, any estimate please?

st...@gmail.com <st...@gmail.com> #11Apr 13, 2021 06:13AM

Facing a similar kind of issue when scrolling the fragments using a ViewPager.

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

Can you update regarding any progress on this issue.

fe...@gmail.com <fe...@gmail.com> #12Aug 13, 2021 08:53PM

I wonder if the new SearchBar has this issue:

https://material.io/blog/android-stable-release-1-8-0

ri...@gmail.com <ri...@gmail.com> #13Sep 24, 2021 05:00PM

Project: platform/frameworks/support
Branch: androidx-main

commit 50f098644adc703ae218b0b7e999629f516a0241
Author: sanura <sanura@google.com>
Date: Thu Mar 02 00:11:35 2023

Add check to only invalidate options menu when contributing menu items

FragmentManager previously appropriately only added
a MenuProvider when the host is a MenuHost **and**
we are at the root fragment that is providing the
menu items. This behavior should be mirrored when
removing a MenuProvider as well, so that only
components that directly contribute menu items will
invalidate the options menu.

Bug: 244336571
Test: all tests pass
Change-Id: I9404ee9fcc9ce6b80d70a93bea720fe4ccf583a0

M fragment/fragment/src/androidTest/java/androidx/fragment/app/FragmentContainerInflatedFragmentTest.kt
M fragment/fragment/src/androidTest/java/androidx/fragment/app/OptionsMenuFragmentTest.kt
M fragment/fragment/src/androidTest/java/androidx/fragment/app/test/FragmentTestActivity.kt
M fragment/fragment/src/main/java/androidx/fragment/app/FragmentActivity.java
M fragment/fragment/src/main/java/androidx/fragment/app/FragmentManager.java

https://android-review.googlesource.com/2465169

ma...@gmail.com <ma...@gmail.com> #14Oct 26, 2021 01:42AM

@13 Fixed when? On which version of which dependency?
Please show what to write on gradle file.

at...@adobe.com <at...@adobe.com> #15Nov 8, 2021 01:06PM

This has been fixed internally and will be available in the Fragment 1.6.0-alpha07 release.

ad...@gmail.com <ad...@gmail.com> #16Nov 12, 2021 12:15PM

@15 I've noticed I can avoid using the fragment dependency and still work fine with fragments. How come?
It's part of the material dependency, perhaps?

gs...@gmail.com <gs...@gmail.com> #17May 15, 2022 11:26AM

The following release(s) address this bug.It is possible this bug has only been partially addressed:

androidx.fragment:fragment:1.6.0-alpha07

jb...@google.com <jb...@google.com> #18Jul 29, 2022 12:06AM

Status: Won't Fix (Infeasible)

@17 What if I don't use this dependency (probably imported automatically by material dependency) ? Use it, still?

br...@google.com <br...@google.com> #19Nov 11, 2022 04:47PM

Status: New (reopened)

@17 I wanted to try what you wrote on the sample I've provided (after I remove my workaround), and for some reason it doesn't let me.
It says "Duplicate class found".
The IDE doesn't provide any useful explanation of what is the class that is duplicated and what to do about it.
Please help.

br...@google.com <br...@google.com> #20Nov 11, 2022 04:48PM

The following release(s) address this bug.It is possible this bug has only been partially addressed:

androidx.fragment:fragment:1.5.6

br...@google.com <br...@google.com> Nov 15, 2022 09:30PM

Assigned to br...@google.com.

ap...@google.com <ap...@google.com> #21Nov 29, 2022 11:53PM

@20 Not 1.6.0-alpha07 ?

br...@google.com <br...@google.com> Nov 30, 2022 12:59AM

Marked as fixed.

il...@google.com <il...@google.com> #22Nov 30, 2022 05:31PM

@21 androidx.fragment:fragment:1.5.6 is a STABLE release. It has the fix we need. The androidx.fragment:fragment:1.6.0-alpha07 is an alpha as it says. 1.6 is "work in progress". 1.6.0 is still not a stable release. Use "alpha" only for testing

ju...@google.com <ju...@google.com> #23Dec 7, 2022 06:35PM

@22 So it's fixed on both. OK

ba...@gmail.com <ba...@gmail.com> #24Jan 30, 2023 09:52PM

the bug still exists with dependencies versions

debugImplementation "androidx.test:monitor:1.6.1"
debugImplementation("androidx.fragment:fragment-ktx:1.6.0-alpha04")
debugImplementation 'androidx.test:core-ktx:1.5.0'

debugImplementation 'androidx.test:rules:1.5.0'
debugImplementation 'androidx.test:runner:1.5.2'

debugImplementation("androidx.fragment:fragment-testing-manifest:1.6.0-alpha04")
androidTestImplementation("androidx.fragment:fragment-testing:1.6.0-alpha04")

ba...@gmail.com <ba...@gmail.com> #25Jan 30, 2023 09:52PM

the launchFragmentInContainer() is running forever

jb...@google.com <jb...@google.com> #26Jan 30, 2023 10:03PM

Please file a new bug with a minimal project that reproduces the issue.