Obsolete
Status Update
Comments
kc...@google.com <kc...@google.com> #2
I'm seeing this as well, and it's happening after navigating to a screen that does not even use compose dependencies. Our flow is:
Non Compose fragment -> Compose fragment -> Non compose fragment -> This crash immediately
Currently troubleshooting, but coming up empty and cannot reproduce on my device, but seeing crashes on client devices.
Non Compose fragment -> Compose fragment -> Non compose fragment -> This crash immediately
Currently troubleshooting, but coming up empty and cannot reproduce on my device, but seeing crashes on client devices.
cu...@google.com <cu...@google.com> #3
What devices and API levels are you seeing this issue?
cu...@google.com <cu...@google.com> #4
Compose version: 1.2.1
Devices: Various devices, seen across Samsung/Pixels/Moto/etc.
Device API levels: Seen on Android 8-13
Devices: Various devices, seen across Samsung/Pixels/Moto/etc.
Device API levels: Seen on Android 8-13
Description
rhi.rockethq@gmail.com, can you attach a snippet or sample app that reproduces this?
Curtis let's take a look when you have a few cycles
Process: com.rhi.rockethq.testing, PID: 15209
java.lang.IllegalArgumentException: Parameter specified as non-null is null: method kotlin.jvm.internal.Intrinsics.checkParameterIsNotNull, parameter errString
at com.rhi.rockethq.Helpers.AccountAuth.BiometricAuthenticationHandler$initializeBiometricPrompt$1$1.onAuthenticationError(Unknown Source:6)
at androidx.biometric.BiometricFragment$2$1.run(BiometricFragment.java:82)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:764)