-
Notifications
You must be signed in to change notification settings - Fork 63
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
Internal inconsistency error (didStartTask) #15
Comments
I see this too. A clean build seems to fix it temporarily. |
Unfortunatelly swiftgen SPM plugin has multiple issues with Xcode 15. For now swiftgen execution must be switched to the build phase scripts. Issues: - SwiftGen/SwiftGenPlugin#14 - SwiftGen/SwiftGenPlugin#15
Unfortunatelly swiftgen SPM plugin has multiple issues with Xcode 15. For now swiftgen execution must be switched to the build phase scripts. Issues: - SwiftGen/SwiftGenPlugin#14 - SwiftGen/SwiftGenPlugin#15
I've seen this problem as well in my project with a local SPM package that uses this SwiftGen plugin. On
together with
Though I've got no idea how to prevent this error yet... |
XCode 15.3 just came out and the message has changed:
It says |
This is not an issue with SwiftGen. It's an issue with Xcode. Please file Feedback requests to Apple so they prioritize this. |
I don't think writing more and more stuff to |
Appreciate this is an Xcode bug and not to do with SwiftGen. There is a comment on swift.org forum which suggests adding a pre-action script to |
https://developer.apple.com/documentation/xcode-release-notes/xcode-16-release-notes
|
Issue Description
Summary:
SwiftGenPlugin causes Xcode to display a build error with the following message:
Issue Details:
The build error described above occurs sporadically and seemingly without any specific trigger. This issue is solely related to Xcode and can be quite frustrating as it distracts developers from focusing on their code. To resolve the issue temporarily, quitting and re-launching Xcode is sufficient.
The problem seems to arise when a change is made to the build plan, such as adding a file, or when initiating a build while Xcode is in an unfortunate indexing stage. This causes Xcode's build cache to become scrambled, resulting in subsequent build failures without any error indication. As a result, the product being built remains stale, and it silently launches outdated code.
The issue persists indefinitely until Xcode is re-initialized. This can be achieved by re-launching Xcode or by performing actions like building for a different target platform or updating a dependency. These actions sometimes fortuitously clear the necessary cache portion, allowing the build to proceed successfully.
This issue affects developers using the SwiftGenPlugin in Xcode and hampers productivity due to the need for frequent manual intervention. A more stable solution or workaround is required to prevent this build error from occurring.
Steps to Reproduce:
Expected Behavior:
The build process should complete successfully without any internal inconsistency errors.
Actual Behavior:
Xcode displays the internal inconsistency error message and subsequent builds fail to produce the expected result, launching stale products instead.
Environment:
https://forums.swift.org/t/internal-inconsistency-error-didstarttask/61194/1
The text was updated successfully, but these errors were encountered: