Fixed
Status Update
Comments
ap...@google.com <ap...@google.com> #3
lblb636@ Thanks for reporting this bug. I just want to confirm that the issue is the call device
button being not responsive according to the uploaded video. It seems like this issue only happened on Windows.
jb...@google.com <jb...@google.com> #4
@3 Why does it occur?
And why only from specific API of Android?
On API 28 for example, it doesn't occur...
Please fix this issue for all API versions of the emulator.
And why only from specific API of Android?
On API 28 for example, it doesn't occur...
Please fix this issue for all API versions of the emulator.
jb...@google.com <jb...@google.com>
ap...@google.com <ap...@google.com> #5
Another similar issue that's related
ap...@google.com <ap...@google.com> #6
RE#4 I need to try this on Windows laptop first and I couldn't repro on MacOS or Linux. But I think this is most likely related to the modem simulator we introduced for API 31. Will need to further investigate.
jb...@google.com <jb...@google.com> #7
@6 There are plenty of issues on emulator API 31 (and on Android 13 emulator). Many glitches. Spend 5 minutes on it and you will notice.
Why isn't the emulator tested more on Windows OS?
Windows OS is more popular than Linux and MacOS combined (on desktop) ...
Why isn't the emulator tested more on Windows OS?
Windows OS is more popular than Linux and MacOS combined (on desktop) ...
my...@gmail.com <my...@gmail.com> #8
@6 Also please check on all versions of the emulator, to see when this issue started, and fix from there.
il...@google.com <il...@google.com> #9
I reproduced this bug on Windows with emulator version 31.2.10-8420304
Description
Component used: Activity Version used: 1.2.0-alpha02
When using the
RequestPermission
orRequestPermissions
contracts, they will only work if using Fragment1.2.0-alpha02
or higher since previous versions ofFragmentActivity
did not callsuper.onRequestPermissionsResult()
(which is howComponentActivity
and henceActivityResultRegistry
get permission results).Ideally, usages of either of these contracts would show a Lint error if the user depends on an older version of Fragments since these contacts won't work. It should have a quick fix that upgrades them to a new enough version of Fragments.