Skip to content
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

Xcodeproj doesn't know about XCBuildConfiguration / baseConfigurationReferenceAnchor #981

Closed
authiatr opened this issue Oct 18, 2024 · 2 comments

Comments

@authiatr
Copy link

authiatr commented Oct 18, 2024

Hello 👋,

Since I migrated a project to Xcode 16 with the new folder project structure and I have the following error when I try to run a Slather command:

[!] Xcodeproj doesn't know about the following attributes {"baseConfigurationReferenceAnchor"=>"305E22322CAC3597003B2EC7", "baseConfigurationReferenceRelativePath"=>"GlobalSettings.xcconfig"} for the 'XCBuildConfiguration' isa.
▸ If this attribute was generated by Xcode please file an issue: [https://github.com/CocoaPods/Xcodeproj/issues/new](https://github.com/CocoaPods/Xcodeproj/issues/new%1B[0m)

This baseConfigurationReferenceAnchor and the XCBuildConfiguration are Xcode's standard attributes.

I made sure that the Slather plugin is up to date, and it seems to use your latest version:

slather (2.8.4)
      CFPropertyList (>= 2.2, < 4)
      activesupport
      clamp (~> 1.3)
      nokogiri (>= 1.14.3)
      xcodeproj (~> 1.25)

Do you have an idea what's wrong?

Thanks,
Robin

@authiatr
Copy link
Author

EDIT 24/10/2024:

The issue is linked to the Xcode project folder structure: I tried rolling back the project structure to groups, and the problem was gone.
This new Xcode folder feature resolves many collaboration issues (e.g., merging conflicts in pbxproj, sorting the files alphabetically automatically), and I assume that the community will massively adopt it.

This Xcodeproj library is quite popular and well-adopted in the iOS open-source world.
I'm curious if the maintainers know about it and if they have already planned to manage these new attributes introduced in Xcode 16.

@authiatr
Copy link
Author

I found out that the community is working on a PR to support Xcode 16. 🙌

I assume it will fix this problem.
I also found many duplicate issues related to the same problem.
I'm closing this one since the contributions are aware and actively working to solve it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant