Skip to content

Investigate and fix Windows app icon showing blue box in production #62

Open

Description

@damoahdominic

Summary

Investigate and resolve the Windows production app icon issue where the app shows a blue box instead of the intended icon.

Goals

  • Identify why the Windows packaged app icon is incorrect in production
  • Implement a fix for the Windows icon pipeline
  • Verify the fix does not break icon behavior on macOS or Linux
  • Document the root cause and validation steps

Scope

  • Inspect branding/build/package config for Windows icon assets and paths
  • Check whether installer, executable, and app window/taskbar icons are all configured correctly
  • Confirm the expected .ico asset exists and contains appropriate sizes
  • Validate cross-platform icon configuration remains intact

Acceptance Criteria

  • Windows production build shows the intended app icon instead of a blue box
  • No regression to icon behavior on macOS or Linux
  • Root cause and fix are documented in the ticket or linked PR

Notes

Requested from OpenClaw Code group chat. Follow repo root AGENTS.md instructions while implementing.

Activity

  1. damoahdominic commented on Apr 3, 2026

    @damoahdominic
    OwnerAuthor

    Root-cause note from initial investigation:

    I inspected the Windows packaging assets/config in apps/editor and found that the build is consistently wired to resources/win32/code.ico for the executable and installer:

    • apps/editor/build/lib/electron.ts → winIcon: "resources/win32/code.ico"
    • apps/editor/build/gulpfile.vscode.win32.js → stamps resources/win32/code.ico into the built .exe via rcedit
    • apps/editor/build/win32/code.iss → SetupIconFile={#RepoDir}\resources\win32\code.ico
    • apps/editor/resources/win32/VisualElementsManifest.xml → tile assets also point at resources/app/resources/win32/code_150x150.png and code_70x70.png

    So the Windows pipeline is not missing an icon path — it is using one specific icon path everywhere.

    The likely issue is the actual contents/quality of resources/win32/code.ico. The current .ico appears to be a single-frame ICO (Pillow only reports a single 256x256 image), which is a common cause of poor/fallback Windows icon rendering in packaged apps. Windows executables/installers generally behave best when the .ico contains multiple embedded sizes (for example 16, 24, 32, 48, 64, 128, 256) rather than just one large frame. A bad/incomplete ICO can show up as a blank/blue/fallback box in some production contexts even when the path/config is correct.

    Also worth checking in the fix:

    • whether the branded OCcode icon asset was regenerated correctly from source artwork
    • whether the same replacement should be applied to installer/tile companion assets (code_70x70.png, code_150x150.png) to keep Windows branding consistent
    • whether any signing/build step is reusing a stale cached executable icon

    Conclusion for now: primary suspected root cause is an incomplete or improperly generated Windows code.ico, not a missing config reference.

    Next step will be to replace/regenerate the Windows icon set with a proper multi-size .ico and validate that macOS/Linux icon assets remain untouched.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions