But according to the docs, it should have that. I am attaching the link for the same. NSEvent windowNumber

Here is the feedback ID: 13403283

I have found the issue. It was happening because Chrome Accessibility was disabled for native and web accessibilty. It can be enabled from chrome://accessibility.

@eskimo Thanks for the response. I am passing the return value of TISGetInputSourceProperty after static casting it to CFDataRef to the CFDataGetBytePtr function.

I am using kTISPropertyUnicodeKeyLayoutData as the property key. This function call with the same code works for our users every time. However, it failed just this once with this issue. Do you know how that is possible?

Yes, I only got a single crash report like this.

Actually, in my app, I am also using accessibility APIs to obtain the app's accessibility object reference. Will that be possible in a sandboxed app? Below is the code I am using: AXUIElementRef app = AXUIElementCreateApplication(targetApplicationProcessID);

Thanks @DTS Engineer, I encountered the same issue again and upon collecting additional data, I discovered that it is affecting users with the Japanese keyboard layout.