Infeasible
Status Update
No update yet.
Comments
kg...@gmail.com
Please include a sample project that reproduces your issue.
kg...@gmail.com
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?
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?
kg...@gmail.com
Hello, have you checked sample project? I hope it will help find the issue.
xa...@android.com
kg...@gmail.com
[Deleted User] <[Deleted User]>
Hello, any update please?
yr...@google.com
Hello
I raised similar issue with this ticket
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?
kg...@gmail.com
@7 Check @5 for a workaround.
yr...@google.com
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?
Any idea on when it will be fixed?
ma...@gmail.com
Hello, any estimate please?
in...@mobileparadigm.co.uk
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.
Can you update regarding any progress on this issue.
sm...@gmail.com
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
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
Description
applicable)
Host OS: OS X
SDK tools version (available in the "About" section of the 'android' tool
UI): 23.0.2
Android Studio version: 0.8.9
STEPS TO REPRODUCE:
1. Build application requiring multiple dex files. Used example found here:
2. Observe app runs correctly on 4.x device.
3. Observe app crashes upon installation on gingerbread device.
EXPECTED RESULTS:
Multidex application runs on gingerbread device.
OBSERVED RESULTS:
Application causes dalvik crash on gingerbread devices:
E/dalvikvm( 2404): LinearAlloc exceeded capacity (8388608), last=6888
E/dalvikvm( 2404): VM aborting
F/libc ( 2404): Fatal signal 11 (SIGSEGV) at 0xdeadd00d (code=1)
...
ADDITIONAL INFORMATION:
I've seen mentions but no definitive evidence that GB devices cannot load dex files over 5Gb. As an experiment I patched dx to produce smaller dex files (see attachement). Building with the modified dx program produced an APK with smaller (no larger than 3Mb) dex files and installation errors did not occur on gb devices.
Due to this I suspect that dx needs to either by default generate smaller dex files to ensure compatibility with gb devices or be tunable in the build configuration for app producers wishing to maintain compatibility with gb.