Receiving +[IMKClient subclass]: chose IMKClient_Legacy logs after updating to MacOS Sequoia

[hooded-shrimp]

Description

I am not sure if this is a MacOS Sequoia bug, or something winit needs to fix.

When I run any winit-based app on my Mac, I get messages like this:

2024-09-25 11:41:42.291 rust-testing[86791:3027734] +[IMKClient subclass]: chose IMKClient_Legacy
2024-09-25 11:41:42.291 rust-testing[86791:3027734] +[IMKInputSession subclass]: chose IMKInputSession_Legacy

When I searched the message, I found that some other non-winit projects are having this issue as well, which makes me think it could be a MacOS Sequoia bug.

macOS version

ProductName:		macOS
ProductVersion:		15.0
BuildVersion:		24A335

Winit version

0.30.5

[einarsi]

I also noticed this just a few days ago, quite possibly right after I updated to Sequoia.

[madsmtm]

Sounds like a macOS bug indeed, a quick internet search reveals a few other instances.

Would be nice if someone could create a bog-standard macOS application in Xcode, perhaps with a text field (since it sounds related to the issue), and see if the problem is present there too?

In any case, I'll leave this issue open for a while for visibility, though I doubt there is anything for us to do.

[hooded-shrimp]

Would be nice if someone could create a bog-standard macOS application in Xcode, perhaps with a text field (since it sounds related to the issue), and see if the problem is present there too?

I tested it with the default Xcode MacOs app template. The issue occurs there as well.

[madsmtm]

Nothing to do then other than reporting the bug to Apple.

[jle-pass]

Hi, do you still have the bug after macOS 15.0.1 update ?

[hooded-shrimp]

do you still have the bug after macOS 15.0.1 update ?

I just updated and checked, the issue is still occurring.

[ShreyanshJoshi]

Hi, do you still have the bug after macOS 15.0.1 update ?

Yes, it is still occurring

[einarsi]

Updated to macOS 15.1 just now, still occurring.

[Commustache]

I also noticed the same problem when using ROOT analysis software. At first it didn't seem to cause any particular problems, but now I have serious problems viewing graphs and the like. As soon as I try to view something the software crashes

[casey]

As a temporary workaround, you can pipe stderr through grep and filter the offending lines:

cargo run 2> >(grep -Ev 'IMKClient|IMKInputSession' >&2)

[kchibisov]

if it just logs it does it really matter? Like hiding the error doesn't make the error not appear at all...

[memark]

I'm getting this when starting my Tauri 2 app on MacOS 15.1.1.

And yes, I think it matters because it adds noise to my logs.