-
-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Codebase for Xcode 16.0 and Swift 6 Compatibility & Optimisation #106
Comments
The new tooling only came out this week, I haven't had a chance to check MarkersExtractor. But most of these warnings are relating to the Marker Data codebase. From the logs it looks like you're adding some conformances in Marker Data to types imported from MarkersExtractor. Things like |
I've done the appropriate refactors and released MarkersExtractor 0.3.10. I have also pushed a PR with changes for Marker Data in response to the refactors: #107 I only touched Marker Data code that was affected by MarkersExtractor. I will leave the remaining build warnings for @milanvarady to resolve, as they all now exclusively deal with the Marker Data codebase. |
…actors Updates for MarkersExtractor 0.3.10 for Xcode 16/Swift 6 compatibility (#106)
@latenitefilms Have shared some details for setting up Workflow Extensions in Xcode 16 https://fcp.cafe/#18th-september-2024 Thanks. |
@milanvarady I just tried to build the app again. The warnings are somewhat lesser than before.
|
Based on this apple developer forum post, this is a known issue in Xcode 16. I believe this Related - |
@milanvarady Thank you for making the tweaks for Xcode 16.0. While the build is successful, there are several warnings shown during the build process.
Are we able to fix and solve them?
@orchetect The warning mentions
MarkersExtractor
andDAWFileKit
? Should the libraries need to be updated for Xcode 16.0 compatibility?Thank you.
The text was updated successfully, but these errors were encountered: