Posts

Post not yet marked as solved
1 Replies
1.4k Views
Reaching out to Apple & developer community to get help regarding an issue seen in Xcode 14.1. We have a workspace which contains multiple .xcodeproj files and also couple of Swift package sources. When I open the workspace and try to build a scheme using Xcode 14.1, I don't see any issue. However, using xcodebuild command throws this issue in CI xcodebuild: error: Failed to build project MyProject with scheme MyProject. Reason: internal error: could not generate PIF because the workspace has not finished loading or is still waiting for package resolution Note that building MyProject scheme was consistently failing with the above mentioned error in CI. After changing the derived data path, the behaviour is flaky. ie, the target fails to build sometimes (with the above mentioned error) and succeeds most of the time. I referred this post and incorporated the suggestion but it didn't resolve the issue. rm -rf ~/Library/Caches/org.swift.swiftpm rm -rf ~/Library/org.swift.swiftpm In order to ensure that the SPM cache is not causing this issue, I also tried clearing the SPM cache using the above statements before building my scheme. Even this didn't help resolve the issue. If anyone knows a fix or a workaround to resolve this issue, kindly share.
Posted Last updated
.
Post not yet marked as solved
4 Replies
1.5k Views
With the recent update to Xcode 14.1 (also seen on Xcode 14.2), the project files get modified automatically every time it is opened. This behaviour is not seen in Xcode 13.4.1. Our project files are sorted alphabetically. Whenever the workspace or .xcodeproj is opened using Xcode 14.1 or 14.2, the pbxproj gets modified and the file references gets sorted based on the alphabetic order of the unique reference identifier as show in the below attachment. Is there a way to prevent this ? If this is a bug on the recent version of Xcode, ie 14.1 or 14.2, could you please acknowledge and address this in the next version ?
Posted Last updated
.
Post marked as solved
2 Replies
1.1k Views
Do we have a maximum limit on the dependencies (which includes Frameworks, Resource bundles, extension targets, etc) and the linked binaries that we add for an app target? Also, I am interested to know if there is any limit on number of static and dynamic framework that can be added/linked to a target. Attaching a sample screenshot to make it more clear
Posted Last updated
.