Hi SweetPad team 👋
I’m encountering an issue where SweetPad reports a task failure / crashes even though the Xcode build succeeds.
The exact error shown is:
🚷 TypeError: c.map is not a function
What happens
• xcodebuild runs and completes successfully
• BUILD SUCCEEDED is printed
• After the build finishes, SweetPad throws the error above
• Cursor then marks the task as failed (exit code -1), even though the build itself succeeded and the app runs fine
Observations
• Happens on a large iOS workspace (hundreds of targets, many SwiftPM dependencies)
• The error appears after the build completes, likely during output parsing
• Occurs both:
• with xcbeautify installed
• and after uninstalling xcbeautify
• Large / noisy stdout seems to trigger it
Example log lines printed before the crash:
Found unhandled resource at .../*.lproj
Found unhandled resource at .../*.xcassets
These are warnings from custom build scripts, not Xcode errors.
I ran xcodebuild directly in terminal works reliably
Environment
• macOS: Version 26.0
• Xcode: Version 26.2
• Cursor: 2.4.22
• SweetPad: 0.1.72
• Project: large iOS workspace with many targets and SwiftPM packages
Thanks for building SweetPad - hoping this helps improve stability for large projects. Happy to provide more logs if needed 🙏
Hi SweetPad team 👋
I’m encountering an issue where SweetPad reports a task failure / crashes even though the Xcode build succeeds.
The exact error shown is:
What happens
• xcodebuild runs and completes successfully
• BUILD SUCCEEDED is printed
• After the build finishes, SweetPad throws the error above
• Cursor then marks the task as failed (exit code -1), even though the build itself succeeded and the app runs fine
Observations
• Happens on a large iOS workspace (hundreds of targets, many SwiftPM dependencies)
• The error appears after the build completes, likely during output parsing
• Occurs both:
• with xcbeautify installed
• and after uninstalling xcbeautify
• Large / noisy stdout seems to trigger it
Example log lines printed before the crash:
These are warnings from custom build scripts, not Xcode errors.
I ran xcodebuild directly in terminal works reliably
Environment
Thanks for building SweetPad - hoping this helps improve stability for large projects. Happy to provide more logs if needed 🙏