Skip to content

Honor logoPath so code apps can have a custom icon (push + maker portal) #361

Description

@rolandk76

Problem
Code apps always show the default placeholder icon in the Power Apps Mobile player and the Apps list — there is no way to set a custom app icon.

Findings

  • pac code init accepts --logoPath and power.config.json has a logoPath field, but @microsoft/power-apps-cli 0.11.0 / power-apps push never uploads it: createAppMetadata (in @microsoft/power-apps-actions PushApp.js) builds the app metadata with only displayName, description, backgroundColor (white) and backgroundImageUri: '' — no logo property. The same metadata is used for both create and save.
  • The maker portal shows no icon/logo option in the code app details page (unlike canvas apps).
  • Verified empirically: a brand-new code app created via power-apps push with logoPath set still has no icon in the player.

Request
Please apply logoPath on pac code push / power-apps push (and on create), and/or add an icon upload to the code-app details page in the maker portal, so code apps can have a branded icon.

Environment
@microsoft/power-apps 1.1.3, @microsoft/power-apps-cli 0.11.0, pac 2.5.1

Activity

  1. eschavez commented on Jun 1, 2026

    @eschavez
    Collaborator

    Thanks for the detailed writeup and for doing the legwork to trace this through the CLI source. We've confirmed the behavior: pac code init / power.config.json accept --logoPath / logoPath, but createAppMetadata in PushApp.js builds app metadata with only displayName, description, backgroundColor, and an empty backgroundImageUri — the logo is never read or uploaded on push or create. The maker portal also has no icon option for code apps today.

    We've logged this for our backlog. It's a meaningful gap for teams building branded or customer-facing apps and we agree it should be addressed. We'll update this issue when we have a planned timeline.

    If you need a workaround in the meantime, the icon can't currently be set programmatically — there's no back-channel approach available.

  2. self-assigned this
    on Jun 23, 2026
  3. locked and limited conversation to collaborators on Jun 23, 2026
  4. converted this issue into a discussion #380 on Jun 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions