manifest version 1.22 icons color32x32 not working

[lnmp4000]

Specifying an entry for color32x32 in the icons section of the manifest.json causes a provision failure.

The icon specified via a relative path is not added to the .zip bundle so the provision fails:

Summary:
1 failed, 3 passed.
You can check and update your app package at ./appPackage/build/appPackage.dev.zip.
(×) Error: The file icon-32x32-color.png could not be found in the app package. 
File path: icon-32x32-color.png, title: Package extraction failed

To Reproduce
Steps to reproduce the behavior:

1. Ensure a valid 32x32 colour png icon exists on the file system
2. Update the manifest.json to reference this icon
3. Provision the Agent
4. See error

Expected behavior
As per the documentation for the manifest version 1.22 a color32x32 icon should be supported.

Name	Type	Maximum size	Required	Description
outline	String	32 x 32 pixels	✔️	A relative file path to a transparent 32x32 PNG outline icon. The border color must be white.
color	String	192 x 192 pixels	✔️	A relative file path to a full color 192x192 PNG icon.
color 32x32	String	32 x 32 pixels		A relative file path to a full color PNG icon with transparent background. Size 32x32.

[m365-agent-toolkit-assistant]

👋 Hi @lnmp4000,

Thank you for reporting this issue! We want to let you know that:

⏱️ Our team will personally review your issue
🎯 You can expect a response within 2 business days

✨ This is an AI-generated initial response
🤖 AI-Generated Preliminary Analysis:

This issue is known—provision failures like yours occur if referenced icons (like color32x32) are missing from the app package .zip. Even if you specify the icon in your manifest, the Microsoft 365 Agents Toolkit (formerly Teams Toolkit) or your toolchain may not auto-include files not referenced by older schema versions, or by default packaging scripts.

Actionable Steps:

1. Ensure you place icon-32x32-color.png in the correct /appPackage (or specified) folder—at the same level as your manifest.
2. Check your project config (m365agents.yml / teamsapp.yml) for custom icon entries. If using custom icon names or paths, explicitly list them.
3. Manually include the icon: Before provisioning/building, verify the icon is in appPackage or copy it there.
4. Rebuild the app package and inspect appPackage.dev.zip—the icon file must be present at the root of the .zip.

If the toolkit is not including this icon on build:

• This could be a limitation/bug awaiting schema or tool update. As a workaround, unzip the package, add the 32x32 color icon, and re-zip before provisioning.

Reference:

• Similar GitHub issue #2701
• Manifest packaging issue

If you need further help, please share your toolkit version and packaging tool (VS Code, VS, CLI), and your manifest’s icons section.

✨We'd love your feedback! Please take a moment to fill out our survey.

---

Note: This is an automated first response generated by AI. A human team member will review your issue and provide a more detailed response soon. We appreciate your patience!

[frankqianms]

Hi @lnmp4000~ Currently, our toolkit doesn't support color 32x32 to be validated in the package. We will support this feature in future release.

[ZeeCapp]

+1 for feature request

[frankqianms]

Closing it as it is already in plan. Please expect it in the future release.