RESOLVED FIXED 276455
Build fails with “'AVAudioSession' is unavailable: not available on macOS”
https://bugs.webkit.org/show_bug.cgi?id=276455
Summary Build fails with “'AVAudioSession' is unavailable: not available on macOS”
sideshowbarker
Reported 2024-07-10 16:28:28 PDT
macOS Sequoia 15.0 Beta (24A5289g) + Xcode 16.0 beta 3 (16A5202i) /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -x objective-c++ […flags…] In file included from /opt/WebKit/Source/WebCore/PAL/pal/avfoundation/OutputContext.mm:37: /opt/WebKit/WebKitBuild/Debug/usr/local/include/pal/cocoa/AVFoundationSoftLink.h:78:33: error:00:00:15 In file included from /opt/WebKit/Source/WebCore/PAL/pal/avfoundation/OutputContext.mm:37: /opt/WebKit/WebKitBuild/Debug/usr/local/include/pal/cocoa/AVFoundationSoftLink.h:78:33: error: 'AVAudioSession' is unavailable: not available on macOS 78 | SOFT_LINK_CLASS_FOR_HEADER(PAL, AVAudioSession) | ^
Attachments
Alexey Proskuryakov
Comment 1 2024-07-10 17:47:31 PDT
We have not done the work to make the beta build yet.
sideshowbarker
Comment 2 2024-07-10 18:18:57 PDT
(In reply to Alexey Proskuryakov from comment #1) > We have not done the work to make the beta build yet. OK, thanks — I was worried that might be the case… So the state of my system is such that I can’t build WebKit at all right now — and I guess there’s no easy way to revert my system to Sonoma. The Software Update widget doesn’t provide that option, at least. I have a backup from before I upgraded to the Sequoia beta. I guess maybe my only practical option for the time being for being able to build WebKit is restore the system from the backup?
Elliott Williams
Comment 3 2024-07-12 13:26:13 PDT
You should be able to download and run Xcode 15 without having to downgrade your OS. The SDK and toolchain we use to build are all part of Xcode, so building with Xcode 15 will build for macOS Sonoma. I'm not 100% confident that what you build will be _runnable_, since WebKit uses private API that are subject to change between major release, but building itself will be fine. If you do need to boot into Sonoma, it may be easiest to install it to a separate APFS volume rather than try to downgrade your main installation.
sideshowbarker
Comment 4 2024-07-15 05:43:44 PDT
(In reply to Elliott Williams from comment #3) > You should be able to download and run Xcode 15 without having to downgrade > your OS. The SDK and toolchain we use to build are all part of Xcode, so > building with Xcode 15 will build for macOS Sonoma. Thanks immensely — I was able to build MiniBrowser with Xcode 15.4 in my Sequoia environment. 🎉 What had thrown me off was: In the Finder the app icon for the Xcode 15.4 shows up with white 🚫 (no) sign over the icon — and when I try to launch it (by double-clicking on it), I get the message “This version of Xcode isn’t supported in this version of macOS.” and it fails to run. But I anyway don’t need to run Xcode (for debugging, I use lldb directly, from the shell, and I do all my editing in vim). It just hadn’t occurred to me (I hadn’t yet bothered to try until I read your message) that even though the Finder is telling me I can’t run the Xcode app, I could still use it for building. > I'm not 100% confident that what you build will be _runnable_, since WebKit > uses private API that are subject to change between major release, but > building itself will be fine. Running is fine too — I’m posting this message from within the MiniBrowser I built. Thanks again very much
Radar WebKit Bug Importer
Comment 5 2024-07-17 16:30:03 PDT
Ahmad Saleem
Comment 6 2024-07-18 05:52:18 PDT
@Mike - should I consider this as 'RESOLVED WORKSFORME' now?
sideshowbarker
Comment 7 2024-07-18 08:05:23 PDT
(In reply to Ahmad Saleem from comment #6) > @Mike - should I consider this as 'RESOLVED WORKSFORME' now? Yup — thanks!
Elliott Williams
Comment 8 2024-07-30 15:58:33 PDT
Just an FYI that WebKit should now be building successfully for macOS Sequoia. Please let me know in https://bugs.webkit.org/show_bug.cgi?id=277116 if you're encountering any build issues.
Note You need to log in before you can comment on or make changes to this bug.