Predictive back gesture leads to fragments not being initialized/resumed correctly [297379023]

Fixed

Bug

Status Update

No update yet.

Description

pa...@gmail.com

created issue #1

Aug 24, 2023 06:09PM

Component used: Fragment

Version used: 1.7.0-alpha03

Devices/Android versions reproduced on: Pixel 6 with Android 14

The short summary of the issue is that once the predictive back gesture is completed (or started and canceled only), the fragments seem to be stacked on top of each other, with the top one displaying its contents without being interactive and the bottom one handling the touch input, which leads to crashes and unexpected behavior.

I've attached a minimal sample project to reproduce and describe the issues:

Navigate through the app and its two fragments without using the back gesture: everything works as expected.
On the second fragment, use the back gesture to navigate back to the first fragment. Then tap on the overflow menu: the app crashes unexpectedly with an IndexOutOfBoundsException in FragmentManager.
Relaunch the app and on the second fragment, start the back gesture but cancel it. Then tap on the overflow menu of the second fragment: it doesn't react anymore. Move slightly left with the finger and tap again to open the menu: this time it opens and the toast says "First fragment", which means the touch input is handled by the first fragment and contents are displayed by the second one. Now pause the app by moving it to the background, then resume it: the contents are fully gone and the overflow menu of the first fragment can still be opened by tapping on the top right corner (but slightly left of it because the overflow menu of the second fragment seems to cover the first). Using the back gesture will bring you back to the first fragment, which is then again acting as described in step 2.
Repeat step 3 without pausing the app, then tap on the disabled(!) "Go to second fragment" button of the second fragment: the app crashes with an IllegalArgumentException because the touch input is again handled by the first fragment and it's (enabled!) top button, so the executed navigation transaction (first to second fragment with the second currently displayed) is obviously illegal.

Hope you guys can fix that for the next alpha, thanks for your amazing work! :)

test-predictive.zip

115 KB

Download

Comments

il...@google.com <il...@google.com> Aug 24, 2023 06:28PM

Assigned to jb...@google.com.

ap...@google.com <ap...@google.com> #2Aug 31, 2023 02:04AM

Seems to be a DNS problem with systems that have 'obtain DNS server address automatically'. Changed my system to a manual setting and the browser etc now work. SDK 2.2 didn't seem to mind the auto setting though.

jb...@google.com <jb...@google.com> #3Sep 5, 2023 03:02PM

Marked as fixed.

Could you please describe how/where you changed your system to a manual setting?

pr...@google.com <pr...@google.com> #4Sep 6, 2023 07:56PM

Based on its date, this issue was originally reported before Android 2.3. Because of the many changes that existed in Android 4.x compared to previous versions, it's very likely that this issue doesn't exist in recent versions of Android like 4.2.2 or newer. Because of the high likelihood that this issue is obsolete, it is getting closed automatically by a script, without a human looking at it in detail. If the issue still exists on a Nexus 4 or Nexus 7 running Android 4.2.2 and is not related to Google applications, please open a new report accordingly.

pa...@gmail.com <pa...@gmail.com> #5Sep 7, 2023 04:16PM

java.lang.IllegalArgumentException: Unable to locate adb
at com.android.tools.idea.run.editor.DeployTargetPickerDialog.<init>(DeployTargetPickerDialog.java:144)
at com.android.tools.idea.run.editor.ShowChooserTargetProvider.showPrompt(ShowChooserTargetProvider.java:113)
at com.android.tools.idea.run.AndroidRunConfigurationBase.getDeployTarget(AndroidRunConfigurationBase.java:600)
at com.android.tools.idea.run.AndroidRunConfigurationBase.doGetState(AndroidRunConfigurationBase.java:281)
at com.android.tools.idea.run.AndroidRunConfigurationBase.getState(AndroidRunConfigurationBase.java:241)
at com.intellij.execution.runners.ExecutionEnvironment.getState(ExecutionEnvironment.java:158)
at com.intellij.execution.runners.BaseProgramRunner.execute(BaseProgramRunner.java:55)
at com.intellij.execution.runners.BaseProgramRunner.execute(BaseProgramRunner.java:50)
at com.intellij.execution.ProgramRunnerUtil.executeConfigurationAsync(ProgramRunnerUtil.java:92)
at com.intellij.execution.ProgramRunnerUtil.executeConfiguration(ProgramRunnerUtil.java:41)
at com.intellij.execution.impl.ExecutionManagerImpl.restart(ExecutionManagerImpl.java:93)
at com.intellij.execution.impl.ExecutionManagerImpl.access$300(ExecutionManagerImpl.java:44)
at com.intellij.execution.impl.ExecutionManagerImpl$3.run(ExecutionManagerImpl.java:442)
at com.intellij.util.concurrency.QueueProcessor.runSafely(QueueProcessor.java:232)
at com.intellij.util.Alarm$Request.runSafely(Alarm.java:356)
at com.intellij.util.Alarm$Request.run(Alarm.java:343)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at com.intellij.util.concurrency.SchedulingWrapper$MyScheduledFutureTask.run(SchedulingWrapper.java:228)
at com.intellij.openapi.application.TransactionGuardImpl$2.run(TransactionGuardImpl.java:315)
at com.intellij.openapi.application.impl.LaterInvocator$FlushQueue.doRun(LaterInvocator.java:435)
at com.intellij.openapi.application.impl.LaterInvocator$FlushQueue.runNextEvent(LaterInvocator.java:419)
at com.intellij.openapi.application.impl.LaterInvocator$FlushQueue.run(LaterInvocator.java:403)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:762)
at java.awt.EventQueue.access$500(EventQueue.java:98)
at java.awt.EventQueue$3.run(EventQueue.java:715)
at java.awt.EventQueue$3.run(EventQueue.java:709)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:80)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:732)
at com.intellij.ide.IdeEventQueue.defaultDispatchEvent(IdeEventQueue.java:755)
at com.intellij.ide.IdeEventQueue._dispatchEvent(IdeEventQueue.java:704)
at com.intellij.ide.IdeEventQueue.dispatchEvent(IdeEventQueue.java:391)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)

an...@gmail.com <an...@gmail.com> #6Jun 20, 2024 08:49PM

voilà ce qu'on m'affiche lorsque j’exécute mon programme

ho...@myrealtrip.com <ho...@myrealtrip.com> #7Oct 15, 2024 03:10AM

Comment has been deleted.

Message last modified on Oct 15, 2024 03:11AM

ha...@gmail.com <ha...@gmail.com> #8Oct 15, 2024 03:12AM

https://issuetracker.google.com/issues/342316801?pli=1

According to above thread, you should either disable predictive back or upgrade the fragment version to 1.8.3