search

dotnet / maui

.NET MAUI is the .NET Multi-platform App UI, a framework for building native device applications spanning mobile, tablet, and desktop.
https://dot.net/maui
MIT License
22.21k stars 1.75k forks source link

+[IMKClient subclass]: chose IMKClient_Legacy +[IMKInputSession subclass]: chose IMKInputSession_Legacy macOS 15.0 #24794

Closed markatosi closed 1 month ago

markatosi commented 1 month ago

Description

Created a new Maui Blazor and or regular Maui application and run the application on Mac Intel. The Maui application window displays and when you click anywhere on the Maui window the following message displays in the JetBrains run log window. The message only displays one time and the application appears to function normally. I tried this with both 8.0.82 and 8.0.90

2024-09-16 09:43:18.090 MauiApp15Hybrid2[12274:200309] +[IMKClient subclass]: chose IMKClient_Legacy 2024-09-16 09:43:18.090 MauiApp15Hybrid2[12274:200309] +[IMKInputSession subclass]: chose IMKInputSession_Legacy

Steps to Reproduce

  1. Create a new Maui application (Either blazor hybrid or regular Maui app)
  2. Run the application on a Mac (I'm using Intel so I can't test silicon at the moment)
  3. Click on the running Maui window
  4. Observe the error in whatever output window you are using

Link to public reproduction project repository

No response

Version with bug

8.0.82 SR8.2

Is this a regression from previous behavior?

No, this is something new

Last version that worked well

Unknown/Other

Affected platforms

macOS

Affected platform versions

Maccatalyst on macOS 15

Did you find any workaround?

No.

Relevant log output

2024-09-16 09:43:18.090 MauiApp15Hybrid2[12274:200309] +[IMKClient subclass]: chose IMKClient_Legacy
2024-09-16 09:43:18.090 MauiApp15Hybrid2[12274:200309] +[IMKInputSession subclass]: chose IMKInputSession_Legacy
github-actions[bot] commented 1 month ago

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Open similar issues:

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

daniel-moulton commented 1 month ago

Perhaps may be of use, but as of today I started getting a similar message in my python project (program also seems to function as normal), so might not inherently be a Maui issue but a MacOS issue perhaps.

python3 main.py
2024-09-17 19:39:41.775 Python[16833:333096] +[IMKClient subclass]: chose IMKClient_Legacy
2024-09-17 19:39:41.775 Python[16833:333096] +[IMKInputSession subclass]: chose IMKInputSession_Legacy

Edit: Upgraded to MacOS Sequoia today, also found this reddit post which seems to support this.

markatosi commented 1 month ago

I also later noticed it in an Electron version of my application but that version wouldn’t fully start. This issue wasn’t happening in a developer beta of Sequoia last month, so it’s something relatively new.

jfversluis commented 1 month ago

I see other reports of this happening for completely other ecosystems so probably something in Sequoia and we don't support that yet, see https://github.com/xamarin/xamarin-macios/issues/20802

Lets reevaluate if this is still a thing once the official support is there and this is still an issue. If that's the case, you probably want to open this issue on the macios repo directly. Closing this for now here!

Anonymouse-dev commented 1 month ago

Immediately after upgrading to sequoia, I started getting these messages on an off in the Terminal: 2024-09-19 02:08:59.925 Python[22821:402672] +[IMKClient subclass]: chose IMKClient_Legacy 2024-09-19 02:08:59.925 Python[22821:402672] +[IMKInputSession subclass]: chose IMKInputSession_Legacy Series([], Name: corr_esm_minmax_30m_slope, dtype: float64)

(corr_esm_minmax_30m_slope,) refers to a specific column in a Pandas dataframe

Nothing has been changed in the code recently, so this is quite certainly a Sequoia issue. App otherwise appear to be functioning normally. Running Python 3.12 on MacOS. OS Version: Darwin 24.0.0

PedanticHacker commented 1 month ago

I have switched from VS Code to Sublime Text on macOS 15.0 (i.e., Sequoia) just to see if Sublime Text will also output those annoying messages. I get the very same messages, as the OP does, when launching my GUI app using either VS Code or Sublime Text.

Can anyone, running the latest beta of macOS 15.1, try to see whether the same output is produced there, if any at all?

dexwert85 commented 1 month ago

yea I have this annoying message too, when ever I am working on my platform layer for my game engine in xcode because I need objc support the program run 3 times the first one is in xcode the the others in terminal to show this messages I thought its an xcode issue but its not when I tried to run it on terminal (I have macOS 15.0.1, I think its an os problem)

couet commented 4 weeks ago

I have it also on may mac running sequoia with my application started for the terminal

dexwert85 commented 3 weeks ago

did they fix the issue?

PedanticHacker commented 3 weeks ago

No, they haven’t fixed the issue yet, not even in version 15.0.1, so perhaps we can hope for a fix in the 15.1 version.

crkhov commented 1 week ago

UPDATE, Going to stop traversing into rabbit hole, but after I post this UPDATE.

EOM

Same with Eclipse 2024-09 (4.33.0) on macOS Sequoia 15.0.1.

java[79662:1266128] +[IMKClient subclass]: chose IMKClient_Legacy
java[79662:1266128] +[IMKInputSession subclass]: chose IMKInputSession_Legacy

I caught a few messages RE: Eclipse's system and file permissions. To decrease time to troubleshoot any further, fixed those issues by explicitly adding Eclipse.app to the list of apps that have Full Disk Access. Re-ran Java app a few times for duplicated messages.

Based on the time that I ran the Java app from Eclipse and Eclipse's Console output, then comparing that time with time of attribution logged on macOS' Console.app, my Java app had triggered macOS' TCC (tccd) Framework.

/System/Library/PrivateFrameworks/TCC.framework/Support/tccd

And the message:

AUTHREQ_ATTRIBUTION: msgID=79662.1, attribution={responsible={TCCDProcess: identifier=SigningServlet-###################-unsigned-eclipse, pid=79408, auid=502, euid=502, responsible_path=/Users/${whoami}/eclipse/java-2024-09/Eclipse.app/Contents/MacOS/eclipse, binary_path=/Users/${whoami}/eclipse/java-2024-09/Eclipse.app/Contents/MacOS/eclipse}, requesting={TCCDProcess: identifier=net.java.openjdk.java, pid=79662, auid=502, euid=502, binary_path=/opt/homebrew/Cellar/openjdk@21/21.0.5/libexec/openjdk.jdk/Contents/Home/bin/java}, },
PedanticHacker commented 1 week ago

I just installed macOS 15.1 (final public version) and this annoyance still persists!

crkhov commented 1 week ago

UPDATE, Going to stop traversing into rabbit hole, but after I post this UPDATE.

EOM

GameBakerStudio commented 1 week ago

This is an issue I've seen everywhere on MacOS Sequoia 15. I've seen it in Tauri, Swing, OpenGL, GLFW, and now Maui. According to someone on the GLFW website, it was likely a debug left in on Apple, which could be related to their switch to SwiftUI or Metal from OpenGL. The warning seems to have no impact on performance or security, and I would simply wait until a future update, and contact AppleINC.

hugle commented 1 week ago

I just updated to Sequoia 15.1, the warning message still persists..

dexwert85 commented 1 week ago

I just updated to Sequoia 15.1, the warning message still persists..

Me too

dexwert85 commented 1 week ago

This is an issue I've seen everywhere on MacOS Sequoia 15. I've seen it in Tauri, Swing, OpenGL, GLFW, and now Maui. According to someone on the GLFW website, it was likely a debug left in on Apple, which could be related to their switch to SwiftUI or Metal from OpenGL. The warning seems to have no impact on performance or security, and I would simply wait until a future update, and contact AppleINC.

I dont think its because of the switch to SwiftUI or Metal because even if you used them it will give you the same issue for example if you use cocoa you will get the issue even if its for apple

PedanticHacker commented 1 week ago

I hope this crappy messages get deleted soon. Annoying as f***.

svenschwarz commented 1 day ago

Apple also seem to give a f*** about that.

nuncio-bitis commented 1 hour ago

I'm getting the same errors for applications built on Mac OS Sequoia for Mac OS Sequoia in Qt, python, and VS Code I've been searching around and it looks like there are bugs in Sequoia that we have to wait for Apple to fix in the next OS version. Unfortunately all Mac OS development grinds to a halt because of this. No applications will run anymore.

PedanticHacker commented 1 hour ago

I’ve noticed in macOS 15.1 that the two messages have slightly changed from saying Legacy to now say Modern.

But, of course, these messages are still annoying, even though they tell me that I’m not using some legacy stuff. I just want them gone!