Did you find out?

figure it out?

use a javascript postMessage to show readiness and then make it visible from the app layer. use a userscript to do this.

Wiping derived data, toggling code signing settings, etc. has not resolved this for me. Looks like this regressed in the past week or so.

@DTS Engineer looks like this behavior has changed in the last day or two for macOS? I used to be able to submit App Store builds with "group.mydomain" (without the team prefix) and it suddenly began breaking today: "Your application bundle’s signature contains code signing entitlements that aren’t supported on macOS" This is with XCode 16.2 Non-Catalyst apps deployed via the Mac App Store may also use an iOS-style app group name (group.*) as long as that group is registered to the app’s team. This is the first criterion mentioned in the release notes (“the app is deployed through Mac App Store”). This seems to no longer be true!

You must put translationtask somewhere that won’t be removed from view hierarchy

Still an issue in 16 beta 6 :) Never getting fixed

I also face this (but haven't seen the half working state yet, it hasn't worked once for me) btw your radar link says not found

figure it out?

that's normal and good. just don't call "stop..." when "start..." gives false.

Simplhy use "Open Recent Logs" and select the .crash file (renamed from .txt) you want to symbolicate

Did you figure this out? I'm running into similar issues with ld: Undefined symbols

No workarounds? I'm facing this with RealmSwift on the main thread in iOS 17. I don't understand how two calls on main thread are able to be "simultaneous"

figure it out?

Ever figure out this one?