Autocomplete `onValueChange` not called when typing when empty, on mobile only

[phelipetls]

Bug report

Current behavior

It seems the Autocomplete callback prop onValueChange is not called when I start typing if the input is empty.

For example, if I reload the page and start typing, onValueChange does not get called even though the actual input value is changed. Same thing happens after clearing the input.

It gets triggered if I type " " (any non-alphanumeric character, such as "%" or ":").

I can reproduce this consistently with https://base-ui.com/react/components/autocomplete#async-search. Weirdly, it only happens on mobile.

See video below:

Screen_Recording_20251028_125910_Samsung.Internet.mp4

Expected behavior

After I clear the input, the onValueChange callback gets called once I start typing again.

Reproducible example

It happens with https://base-ui.com/react/components/autocomplete#async-search for me.

Base UI version

For example v1.0.2

Which browser are you using?

Firefox and Chromium-based web browsers (Samsung Internet).

Which OS are you using?

Android.

Which assistive tech are you using (if applicable)?

None.

Additional context

Provide any additional context that might help us identify the problem and find a solution.

[mj12albert]

@phelipetls Hey does it repro on HEAD for you? https://master--base-ui.netlify.app/react/components/autocomplete#async-search

Also any chance you're using the (default?) samsung keyboard with predictive text on (also the default I believe)? 🧐

[mj12albert]

I think it's the same issue fixed by #2944, and testing with browserstack on main it should be fixed:

Screen.Recording.2025-10-29.at.12.37.32.AM.mov

[phelipetls]

@phelipetls Hey does it repro on HEAD for you? https://master--base-ui.netlify.app/react/components/autocomplete#async-search

No, in this link it seems to be fixed already on the same browser I recorded the video (Samsung Internet)

[phelipetls]

Also any chance you're using the (default?) samsung keyboard with predictive text on (also the default I believe)? 🧐

I believe so, I didn't change any settings and I'm using One UI 8.

Thank you for noticing it is already fixed, I will be waiting for the new release.

[atomiks]

There's a workaround for beta.4, if you install the utils package that's tagged as latest from npm

import { isAndroid } from '@base-ui-components/utils/detectBrowser';

<Autocomplete.Input 
 onCompositionStart={(event) => {
   if (isAndroid) {
     event.preventBaseUIHandler();
   }
 }}
/>

Or you can use the current HEAD commit version with our pkg.pr.new canary releases if the breaking changes don't affect you:

pnpm i https://pkg.pr.new/@base-ui-components/react@ad0190c7
pnpm i https://pkg.pr.new/@base-ui-components/utils@ad0190c7