"disable adaptive cards" - sample does not work in Version 4.19.1 of botframework-webchat

[MGwiozda]

Is it an issue related to Adaptive Cards?

Yes, this is an Adaptive Card issue, however it only repro on Web Chat.

Is this an accessibility issue?

No

What version of Web Chat are you using?

Latest production

Which distribution are you using Web Chat from?

NPM

Which hosting environment does this issue primarily affect?

Web apps

Which browsers and platforms do the issue happened?

Browser: Chrome (latest)

Which area does this issue affect?

Attachment: Adaptive Card

Which theme pack does this issue affect?

I did not test it on other theme packs

What is the public URL for the website?

No response

Please describe the bug

The disabling of adaptive cards worked in Version 4.17.0. In Version 4.19.1 it's broken.

Aufzeichnung.2026-06-19.090559.mp4

Do you see any errors in console log?

No

How to reproduce the issue?

1. Use the adaptive-cards sample: https://github.com/microsoft/BotFramework-WebChat/blob/main/samples/05.custom-components/l.disable-adaptive-cards/index.html
2. use an chatbot with a adaptive cards dialog which sends subsequent adaptive cards
3. send an adaptive card

What do you expect?

the before last adaptive card gets disabled

What actually happened?

the before last adaptive card doesn't get disabled

Context

It looks like the attachmentMiddleware is now called only once: when the adaptive card is initially rendered. In Version 4.17.0 the middleware was called for every new message in the bot. This behaviour change is probably the cause for the broken feature.

[MGwiozda]

I tried the following code in the attachmentMiddleware:

React.useEffect(() => {
            const updateRecentMessage = () => {
                const { activities } = store.getState();
                const messageActivities = activities.filter((activity) => activity.type === 'message');
                const isRecent = messageActivities[messageActivities.length - 1] === activity;
                setRecentBotMessage(isRecent);
            };
            updateRecentMessage();
            return store.subscribe(updateRecentMessage);
        }, [activity]);

It's causing a weird behaviour. When the latest card is clicked, the before last gets focused.

Aufzeichnung.2026-06-19.094010.mp4