Add a Lint warning when using the RequestPermission contract and not using Fragment 1.2.0-alpha02 or higher [152554847]

Fixed

Bug

Status Update

No update yet.

Description

il...@google.com

created issue #1

Mar 26, 2020 11:13PM

Component used: Activity Version used: 1.2.0-alpha02

When using the RequestPermission or RequestPermissions contracts, they will only work if using Fragment 1.2.0-alpha02 or higher since previous versions of FragmentActivity did not call super.onRequestPermissionsResult() (which is how ComponentActivity and hence ActivityResultRegistry 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.

Comments

ap...@google.com <ap...@google.com> #2Jun 17, 2020 03:38AM

Thank you for the report. We will try to fix this soon. In the meantime, could you please start the emulator from the console (see the commands below), open the camera app to crash it and attach the output, it might help to figure out what the problem is:

cd /Users/YOUR_USERNAME/Library/Android/sdk/emulator
./emulator -list-avds
./emulator -verbose -avd YOUR_AVD_FROM_PREVIOUS_STEP

if there is a crash report to send, please send it and attach the report id.

ap...@google.com <ap...@google.com> #3Jun 17, 2020 03:38AM

We got a crash report (thanks JP): 872e3b20bc34905b. It says EXC_BAD_INSTRUCTION / 0x00000001 and the console also says "Illegal hardware instruction". I suspect the new MacOS brought a new hypervizor which causes this behavior. Haitao, could you please take a look?

jb...@google.com <jb...@google.com> #4Jun 17, 2020 02:48PM

Marked as fixed.

We have quite some crashes like this:

product_name="AndroidEmulator" AND crash.Reason="EXC_BAD_INSTRUCTION / 0x00000001" AND cpu.Architecture="arm64"

jb...@google.com <jb...@google.com> Jul 2, 2020 01:00AM

Status: Assigned (reopened)

ap...@google.com <ap...@google.com> #5Jul 7, 2020 05:45PM

The most of crashes happen here:

vVertical_Scale_ARGB_8888_Accelerate
vImageVerticalShear_ARGB8888
vImageVerticalShear_ARGB8888
vImageScale_ARGB8888

vRotateClockwise270Degree_ARGB8888_Accelerate2
vRotate_90_ARGB_8888_270Degree_Accelerate2

ap...@google.com <ap...@google.com> #6Jul 8, 2020 09:31PM

I suspect EXC_BAD_INSTRUCTION happens in vImageRotate90_ARGB8888 and vImageScale_ARGB8888 which are used by webcam on MacOS.

jb...@google.com <jb...@google.com> #7Jul 8, 2020 09:37PM

Marked as fixed.

With complete honesty, I have to say that I’m extremely disappointed by the handling of this issue by google and by the fact that it came out in the first place. I need to use android studio for work purposes and I am forced to switch to a different machine. Mac OS Sonoma has been in beta testing for months and google has had plenty of time to ensure the application would be properly running. I expect this issue to have the maximum priority and to be solved very soon.

my...@gmail.com <my...@gmail.com> #8Jul 22, 2020 11:51PM

Hi rforzani22, I am sorry for this experience. This bug is my top priority. We expect a fix to be merged within a week. You should be able to download a build directly from our build server (https://ci.android.com/builds/branches/aosp-emu-master-dev/grid) once the fix is merged. The release process will take some additional time.

il...@google.com <il...@google.com> #9Jul 22, 2020 11:56PM

Thanks for making it a top priority, looking forward for the fix, good luck!