Claude Code makes changes beyond the scope of what was requested
Bug / Behavior Issue
User asked for a single, specific change: make the App Store icon have a dark background instead of white. Claude Code changed the shared asset catalog icons that are used across the entire app (all popups, all targets), instead of creating a separate icon for the App Store submission only.
This broke the icon appearance in every popup/dialog across both the Pro and Lite targets, requiring the user to restore from backups and re-archive/re-upload to the App Store — adding yet another build number to an already messy submission.
Root cause
Claude Code didn't consider the blast radius of the change. The user asked to change one thing (the App Store listing icon) and Claude modified a shared asset that affected everything.
Expected behavior
When asked to make a targeted change, Claude Code should:
- Understand the scope of the request
- Identify what is shared vs. isolated
- Only modify what's necessary — in this case, create a separate 1024x1024 icon for the App Store upload, not overwrite the shared asset catalog
Impact
- Broke icon appearance across entire app (black squares in all popups)
- Required restoring from backup
- Required yet another App Store build upload (build 4, when user was already frustrated about builds 1-3)
- Significant loss of user trust
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗