Status Update
No update yet.
Comments
fu...@google.com
1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?
xi...@google.com
[Deleted User] <[Deleted User]>
Tested on Android 12 Emulator with custom executor, but cannot repro this issue.
ap...@google.com
-
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.
xi...@google.com
pr...@google.com
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
CAMERAX VERSION: 1.3.0-alpha07
CAMERA APPLICATION NAME AND VERSION: Aperture (https://github.com/LineageOS/android_packages_apps_Aperture ), version 13
ANDROID OS BUILD NUMBER: TQ2A.230505.002
DEVICE NAME: Google Pixel 7 Pro
DESCRIPTION: CameraController is still using OutputSize, which is a class only used by CameraController. Now that ResolutionSelector exists, it should be migrated to that (with the advantage of also adding setAllowedResolutionMode control). A patch has been sent to AOSP Gerrit to implement this change:https://android-review.googlesource.com/c/platform/frameworks/support/+/2621689
LIST ANY EXPERIMENTAL FEATURES:
STEPS TO REPRODUCE: Not applicable
OBSERVED RESULTS: Not applicable
EXPECTED RESULTS: Not applicable
REPRODUCIBILITY: Not applicable
ADDITIONAL INFORMATION: N/A
CODE FRAGMENTS (this will help us troubleshoot your issues):https://android-review.googlesource.com/c/platform/frameworks/support/+/2621689