The bug report information is here: FB12279185 (os_log fails to display in Xcode 15's console when an argument is private and instead displays nothing, which is misleading)

Ah yes. That makes a lot more sense. I did finally discover the privacy tag in the documentation, but you’re right it’s pretty misleading not to see that marker. I’ll file a report as soon as I can. By the way, is there no way to set the default to public? I just wanted to replace 100s of printfs with os_log to take advantage of the new Xcode 15 console features. I was going to do a hack solution in which I preprocessed strings and replaced %s with %{public}s, #define MY_LOG(fmt_, …) \ os_log_info(OS_LOG_DEFAULT, gen_public_fmt(fmt_), __VA_ARGS__) but os_log asserts on non-constant format strings.

WebXR will be available behind an experimental flag, so they’re working on it.

There’s some new functionality to help with animation, it seems: CAMetalDisplayLink

I’m getting the feeling that OffscreenCanvas is incomplete and has never been exposed. Maybe the release notes serve only to tell us about the implementation progress.

I see it’s in multiple places in the Safari technology preview release notes, but yes, I cannot access Offscreen Canvas from the window. Does anyone know how to access it, if it’s even possible?

Apparently it's been resolved in 13.2: " Project Navigator Resolved Issues Xcode performance is no longer affected when source code displays several warnings and errors. (84533671) " Of course we have to try it. It's not necessarily entirely fixed.

Has anyone received replies regarding their bug reports? For such a big issue, it is taking a very long time to get feedback.

Is there a way to build to ios 15 and macOS 12 using Xcode 12? I am delaying upgrading due to this. I think the answer is “no,” so I am stranded because my large project is impossible to edit realistically. How can can an issue like this get past v .0?

Has anyone filed a bug report?

Xcode 13.1 has been released, but does it actually address this issue at all?

This is still a problem and unexpected behavior. Dictation or Siri need to be on for recognition to work again, seemingly (as @adadas said) , but iOS 14 had no such requirement. There is also no way to really prompt the user to activate this setting programmatically, and it puts undue burden on them when an app should just have its own permissions that the user approves/authorizes.

Any updates? I haven't received word via the bug report or code-level support request (the latter of which is kind of a waste).

I've confirmed that iOS 14.8 is still just fine on a spare non-upgraded iPad.

Side-note: how were you able to get it to work in the first place? I am running a localhost python3 server to test and I can't get the page to request access to the microphone in Safari--only in Chrome.