Thanks for chiming in. I’ve been fixing some bugs caused by the moving to a new project because, for example, some build settings for the Info.plist do not match the previous settings. I wI’ll check if that solved my problem with the previous origimal project.
jvarela
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
To reply my own question, after a lot of tinkering I was able to solve my problem by:
Moving the whole project to a freshly created project; AND by
Removing an Xcode custom setting that put the build folder inside the project folder instead of the default path, which is inside the DerivedData folder.
This solved all my issues, but what a bummer with lost time. It seems that the new build system does not like us to change this default setting on MacOS Sequoia while working perfectly well on Sonoma.
Hope this helps someone!
I have also the same issue. Please fix this. I want to turn off the Explicitly Built Modules but I can't because the Swift compiler settings are missing in Xcode 16.1.
Thanks for the reply. Yes, you were on the mark. This was a warning that if you are running on macOS Sonoma you must use the new API requestFullAccessToEvents(completion:) or you won't have access to Calendar database.
I was also bitten by this problem. If this happens, it is like the OP said: you still have the VALID_ARCHS setting on your build settings. The trick is to scroll ALL THE WAY down to the user-defined build settings, because when this setting became deprecated it was moved down to the bottom of your build settings. Once you DELETE (yes, delete it with the delete button) this build setting, another option called My Mac will show up besides the My Mac (Rosetta) option and then you can build an Apple Silicon version of your Mac app. If you have more than one target, you need to repeat this for each target you have on your project.
Another thing I learned is that at least on Monterey if you do not include a PkgInfo file containing the text "BNDLhbwr" (without the quotes) inside your help bundle, Finder will not recognize it as such and it will continue to display it as a normal folder. I discovered this through trial and error using Xcode's PkgInfo as a starting point to force this.