Throw error when attempting to registerForActivityResult after CREATED [165435866]

Fixed

Bug

Status Update

No update yet.

Description

jb...@google.com

created issue #1

Aug 19, 2020 03:09AM

Much like was done for Fragments in b/162255449, When using the ActivityResultRegistry with a LifecycleOwner, the latest possible time that register() should be called is while the lifecycle is CREATED. This ensures that any registered callbacks are always registered in the same exact order.

If there is an attempt to register after the LifecycleOwner is STARTED, we should throw.

This is different from b/162255449 because fragments don't move their Lifecycle until after their lifecycle callbacks (another joy of the multiple fragment lifecycles). Once b/127528777 is fixed, this will go for fragments as well.

Comments

ap...@google.com <ap...@google.com> #2Sep 1, 2020 08:10PM

Update: I was able to downgrade to 32.1.10 and I can confirm it's smooth again. The issue is indeed in emulator version 33.1.1

jb...@google.com <jb...@google.com> #3Sep 1, 2020 09:05PM

Marked as fixed.

It's happening to me too and I also confirm that reverting to 32.1.10 fixes the issue.

We should have an easier way of reverting versions. AS should allow picking the version similarly to how we already do for the other tools in SDK manager.

pe...@gmail.com <pe...@gmail.com> #4Oct 9, 2020 11:43AM

Hi,

would you try to turn on hardware GPU rendering (instead of auto GPU) and see if it fixes this issue?

jb...@google.com <jb...@google.com> #5Oct 9, 2020 04:59PM

Hi,

I'm currently not able to change this option, it is greyed out.

ba...@gmail.com <ba...@gmail.com> #6Nov 6, 2020 08:17PM

Hi,

there are 2 ways to set it:

1. use a google_apis image (instead of google_apis_playstore). it will re-enable the option.
2. go to your avd folder (usually located in ~/.android/avd/your_avd_name.avd/), open config.ini and hardware-qemu.ini, then modify those lines:

hw.gpu.enabled=yes
hw.gpu.mode=host

ba...@gmail.com <ba...@gmail.com> #7Nov 6, 2020 08:18PM

Hi,

Yes, option 2 fixes the issue (which also persists on 33.1.2 btw). Even though I get a warning when I start the emulator (see attachments).

Will this option be enabled "out of the box" in a future version?

il...@google.com <il...@google.com> #8Nov 6, 2020 08:26PM

Hi,

we suspect a bug in gpu detection logic on Mac M1, and will try to address it in upcoming releases.

am...@gmail.com <am...@gmail.com> #9Mar 25, 2021 01:56PM

Hi Devki,

would you help to cp aosp/2451107 to next stable and canary releases? Thank you!

wa...@gmail.com <wa...@gmail.com> #10Nov 17, 2021 02:30PM

Hi Devki,

Could we cherry-pick it to canary release as well? Thanks!

re...@gmail.com <re...@gmail.com> #11Oct 13, 2022 01:33AM

@yahan it will be picked up in the next canary since we are doing snaps!

ku...@gmail.com <ku...@gmail.com> #12Sep 9, 2023 01:29PM

Comment has been deleted.

Message last modified on Sep 9, 2023 01:29PM

ow...@gmail.com <ow...@gmail.com> #13Sep 19, 2023 02:51AM

Was able to force the emulator to use the host GPU by opening it via the terminal with

./emulator -avd Resizable_API_33 -gpu host

jb...@google.com <jb...@google.com> #14Sep 19, 2023 02:14PM

I believe this is still happening in 33.1.10