-
Notifications
You must be signed in to change notification settings - Fork 86
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
Bug: Missing clangs arg count #2881
Comments
Workaround was to delete all caches, including our Bazel disk cache |
I wonder, are you following the suggestion here to get Bazel to pick up correctly the change in Xcode versions? https://github.com/bazelbuild/rules_apple/blob/master/doc/common_info.md#xcode-version-selection-and-invalidation |
@BalestraPatrick Yeah we have that all setup (correctly i hope). The command line builds are fine its just when generating the project that we see the failure. |
Was |
That file should never be empty ( rules_xcodeproj/tools/generators/lib/PBXProj/src/WriteTargetSwiftDebugSettings.swift Lines 47 to 53 in 66dfa1e
|
The one thing we did which i think caused other build failures (and forced us to use our |
Probably. I would need a repro to dig into this more. Looking at the code, it doesn't seem like this condition should be possible outside of cache poisoning. |
We had another engineer report the same error (different target). They reported deleting a target and then trying to generate a project. I don't believe an Xcode change was involved in this case but need to check with them. Going to try to get a repro, so far haven't been able to myself. |
Consistently hitting this just now in an internal project, tried to clean everything an no luck. Trying to wipe my disk cache now to see if that unblocks me. If I manage to find a repro will share it here as well. EDIT: confirmed that after deleting my disk cache directory the issue is gone |
An engineer just reported this again, should we reopen? It's not immediately obvious what's causing this but clearing out caches seems to fix this |
For this recent case I don't believe there was any Xcode switching involved |
Until we have a repro, I don't know what we can do. I'm not sure it's not a remote cache things, or a Bazel bug, or if it's something in rules_xcodeproj. I also asked some questions about the content of files. I'm not even sure what the symptom is, let alone the root cause. Do you have more information on any of that? |
Yeah I don't really know either, personally never run into it. From the errors we've seen it's the debug_settings file but I haven't been able to look deeper at the contents, etc |
I got a similar (but slightly different) report on internal CI, so going to reopen this (still without repro steps though):
|
Description
A user reported an issue where they were on one commit using Xcode 15.1 where things were working correctly. They switched to a commit which uses Xcode 15.0.1 and run into generation errors during project generation:
Reproduction steps
From what what was reported to me:
Expected behavior
The project generates correctly
rules_xcodeproj version
1.15.0
Xcode version
15.1 -> 15.0.1
Bazel version
6.4.0
rules_apple version
3.1.1
rules_swift version
1.13.0
Additional information
No response
The text was updated successfully, but these errors were encountered: