Status Update
Comments
al...@google.com <al...@google.com> #2
1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?
al...@google.com <al...@google.com>
al...@google.com <al...@google.com> #3
Tested on Android 12 Emulator with custom executor, but cannot repro this issue.
ap...@google.com <ap...@google.com> #4
-
Second crash in the description is from a real device. Experienced it myself on two different Xiaomi phones, plus lots of crashes from users in the Google Play console.
-
Dynamic features are not used in the application.
As a wild guess, I have downgraded build tools from 31.0.0 to 30.0.3, compileSdk from 31 to 30, and moved all work with Language ID to the service in a separate process (just to be sure that crash can kill secondary process instead of main). This combination is in beta for 2 days by now and I don't see any SIGSEGV crashes.
lo...@gmail.com <lo...@gmail.com> #5
Hmm, I feel the crash might be something related to separate/secondary process.
I also changed compileSdk and targetSDK to 31 but still cannot repro this issue.
Description
Library used: AndroidX Annotations
Version used: 1.2.0-beta01
Hello!
It'd be very helpful to have the
@RestricTo
annotation fromandroidx.annotation
be@Documented
so we see it right into the IDE.It's especially important for CameraX users as there's many restricted symbols appearing in auto-completion, on its only when we try to use them that we see the error, and there's no way to see it's restricted from the quick documentation popup.
Adding the
@Documented
annotation will help to spot them.Thank you for considering, have a great day!
Louis CAD