ActiveFocusListener not firing for false values [395548918]

Verified

Bug

Status Update

No update yet.

Description

ys...@google.com

created issue #1

Feb 10, 2025 10:03AM

Component used: ActiveFocusListener Version used: 1.5.0-alpha09 Devices/Android versions reproduced on:

Found investigating https://b.corp.google.com/issues/395547986

Use wear-os-samples ComposeStarter with latest alphas.

Logging added here https://github.com/yschimke/wear-os-samples/commit/10eae5e555fb7cee04f6f22f142725ab65ce445f

---------------------------- PROCESS STARTED (20522) for package com.example.android.wearable.composestarter ----------------------------
10:00:13.802  I  GreetingScreen true
10:00:23.967  I  ListScreen true
10:00:26.494  I  GreetingScreen true

Comments

st...@google.com <st...@google.com> Feb 10, 2025 02:29PM

Assigned to ss...@google.com.

ys...@google.com <ys...@google.com> #2Feb 10, 2025 04:49PM

A couple of questions:

1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?

Message last modified on Feb 10, 2025 04:49PM

ss...@google.com <ss...@google.com> #3Feb 10, 2025 04:58PM

Tested on Android 12 Emulator with custom executor, but cannot repro this issue.

ap...@google.com <ap...@google.com> #4Feb 11, 2025 10:51AM

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.

ss...@google.com <ss...@google.com> Feb 11, 2025 10:53AM

Marked as fixed.

gr...@google.com <gr...@google.com> #5Mar 3, 2025 03:23PM

Verified by gr...@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.

Issue 395548918