ActivityResultLauncher fails in Fragment.onCreate() [161464278]

Fixed

Bug

Status Update

No update yet.

Description

su...@twofortyfouram.com

created issue #1

Jul 16, 2020 08:08PM

Component used: Fragment
Version used: 1.3.0-alpha06

STEPS TO REPRODUCE
1. Try calling ActivityResultLauncher.launch() during Fragment.onCreate()

RESULTS
Actual: Exception is thrown because fragment is not in created state. Exception is included below.
Expected: No exception is thrown.

NOTES
I called super.onCreate() first. The issue seems to be that the ActivityResultLauncher is looking at the lifecycle to be set to CREATED.

java.lang.IllegalStateException: Operation cannot be started before fragment is in created state
at androidx.fragment.app.Fragment$8.launch(Fragment.java:3351)
at androidx.activity.result.ActivityResultLauncher.launch(ActivityResultLauncher.java:42)
at com.twofortyfouram.locale.sdk.host.edit.AbstractSupportPluginEditFragment.onCreate(AbstractSupportPluginEditFragment.java:173)
at androidx.fragment.app.Fragment.performCreate(Fragment.java:2867)
at androidx.fragment.app.FragmentStateManager.create(FragmentStateManager.java:444)
at androidx.fragment.app.FragmentManager.moveToState(FragmentManager.java:1287)
at androidx.fragment.app.FragmentManager.moveToState(FragmentManager.java:1444)
at androidx.fragment.app.FragmentManager.moveFragmentToExpectedState(FragmentManager.java:1522)
at androidx.fragment.app.FragmentManager.moveToState(FragmentManager.java:1575)
at androidx.fragment.app.BackStackRecord.executeOps(BackStackRecord.java:455)
at androidx.fragment.app.FragmentManager.executeOps(FragmentManager.java:2299)
at androidx.fragment.app.FragmentManager.executeOpsTogether(FragmentManager.java:2084)
at androidx.fragment.app.FragmentManager.removeRedundantOperationsAndExecute(FragmentManager.java:2022)
at androidx.fragment.app.FragmentManager.execPendingActions(FragmentManager.java:1924)
at androidx.fragment.app.FragmentManager$5.run(FragmentManager.java:489)
at android.os.Handler.handleCallback(Handler.java:873)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:193)
at android.app.ActivityThread.main(ActivityThread.java:6669)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)

Comments

il...@google.com <il...@google.com> #2Jul 17, 2020 12:23AM

Assigned to jb...@google.com.

Please include a sample project that reproduces your issue.

ap...@google.com <ap...@google.com> #3Jul 28, 2020 05:32PM

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?

jb...@google.com <jb...@google.com> #4Jul 28, 2020 06:04PM

Marked as fixed.

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

va...@gmail.com <va...@gmail.com> #5Oct 21, 2023 07:45PM

@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.

jb...@google.com <jb...@google.com> #6Oct 23, 2023 03:06PM

Hello, any update please?

pa...@wagwalking.com <pa...@wagwalking.com> #7Nov 20, 2023 05:18PM

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?

il...@google.com <il...@google.com> #8Nov 27, 2023 06:37PM

@7 Check @5 for a workaround.