Kevin, first of all, thank you very much for coming back to my question again. Only one last question: What do you mean by AppKit runloop modes? Are they accessible in a Catalyst environment? Thanks Markus

Thank you for your answer. [quote='807092022, DTS Engineer, /thread/764006?answerId=807092022#807092022'] So, my main advice here is to rewrite things so that you stop doing this. It might be possible to get this working (see below) [/quote] I do not find anything below you referred to. Can you please advise? Thanks and regards Markus

Same here on a M1 machine. Very annoying during development.

I finally also got voice chat to work again. The solution was to not play any other game sound while voice chat is active. In the past the game sound was muted by iOS automatically, now you have to do it yourself. If you try to play even one sound, the voice chat stops immediately. But I have one question to the guys who seems to have more voice chat experience here (by the way AirWings is pretty cool): the volume the voice chat is playing is 100%, not matter if the volume slider is at 0 or 100, and not matter if I call setVolume:0.0 or setVolume:1.0, no matter if I call this before or after I active the voice chat etc. It is really very loud. Does anybody has an idea what I'm doing wrong? Thanks a lot for any help Markus

Is there a reason why the new placeholder function does not have access to the Intent data? It would be useful to be able to access some settings from the IntentConfiguration to e.g. use colors the user selected also for the placeholder view. Or did I miss something? Markus

Well, there is not much to elaborate. WidgetKit is Swift only, so using Objective-C sources needs a bridge header file. When I'm using a bridge header file and add an Objective-C source to my WidgetKit project, then the error you are asking for appears. If I remove both, the error file is gone. This explains why a new project does not show this error, but an existing project does. Unfortunately I do not have a solution to this problem, so I'm hoping that Apple will fix this issue in one of the next Xcode beta versions. Or some new background about the problem will be revealed. Unfortunately this thread is marked as solved now, which it definitely isn't :-( Markus

I'm running into the same problem. I nailed it down to my bridging header and the references Objective-C class file, which is also included to the project. If I remove the bridging header, and the Objective-C file, the compile is successful, and the errors are gone. Any more ideas are highly welcome, because converting this Objective-C class to Swift would be a nightmare. Thanks Markus

I know your post is pretty old, but I'm struggling at the same problem. My GKVoiceChat routines worked for some time, but now they are broken. I've tried anything suggested in this thread, but nothing. Does voice chat in your app still work with iOS 13.4.1?RegardsMarkus