Steps to reproduce:

This seems to happen in any UIA edit field. I've seen this in Unigram, but it occurs in other places as well.

1. Go into an edit field that causes the issue, and tab or otherwise navigate out of it.

Actual behavior:

An error is reported in the log.

Expected behavior:

No error.

System configuration

NVDA installed/portable/running from source:

Installed

NVDA version:

alpha-23940,c6aa7712

Windows version:

Windows 11, build 22471.

Name and version of other software in use when reproducing the issue:

Unigram 8.1.6643.0.

Other information about your system:

N/A

Other questions

Does the issue still occur after restarting your computer?

Yes

Have you tried any other versions of NVDA? If so, please report their behaviors.

Yes, alpha-23903,fb4466ee works normally. This seems to have introduced some time around alpha-23913,cfeb3d27.

If NVDA add-ons are disabled, is your problem still occurring?

Yes.

Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?

Yes.
Debug log fragment.
Input: kb(laptop):tab
IO - speech.speech.speak (09:37:02.432) - MainThread (8220):
Speaking [LangChangeCommand ('en_US'), 'Attach media', 'button', CancellableSpeech (still valid)]
ERROR - queueHandler.flushQueue (09:37:02.464) - MainThread (8220):
Error in func NVDAObject._reportErrorInPreviousWord..delayedDetection
Traceback (most recent call last):
File "queueHandler.pyc", line 55, in flushQueue
File "NVDAObjects_init.pyc", line 1067, in delayedDetection
File "NVDAObjects\UIA_init.pyc", line 764, in getTextWithFields
AttributeError: 'NoneType' object has no attribute 'UIAElement'