In version 1.4.1, which ZAP tool is being used

[AkihiroN]

When using the version v2024.08.14-nightly described in the Wiki, configuring and outputting with the ZAP tool does not include GeneralCommissioning inside DispatchSingleClusterCommand in IMClusterCommandHandler.cpp. This causes a build error.
Could you please explain the cause?

[STTwo-32]

Hello @AkihiroN 

Could you please give more details about this behavior and how to reproduce it.

Best Regards.

STTwo-32

[AkihiroN]

Understood.
The development environment is as follows:

・X-Cube-Matter: v1.4.1

・zap tool: v2024.08.14-nightly

・STM32CubeIDE: v1.17

Base project: Lighting-App-SBSFU

・Reproduction steps:
Step 1: Use the zap tool to create a .zap file (attached)
Step 2: Use generate.py and codegen.py to generate the necessary files
Step 3: Rename the Lighting-App-SBSFU project and open it in STM32CubeIDE
Step 4: Link the generated files accordingly
Step 5: Build the project. The build succeeds.
Step 6: Execute commissioning. When executing, commissioning fails because there is no case statement for case Clusters::GeneralCommissioning::Id: in IMClusterCommandHandler.cpp (GeneralCommissioning server is enabled in the ZAP tool)

Why is the DispatchSingleClusterCommand for GeneralCommissioning not generated even though GeneralCommissioning is enabled in the ZAP tool?
In the Lighting-App-SBSFU project inside X-Cube-Matter v1.4.1, the IMClusterCommandHandler.cpp within the lighting-app does have GeneralCommissioning enabled. However, using lighting-app.zap and generating files with zap tool v2024.08.14-nightly results in the same issue.

Could you please tell me the version of the zap tool used for the Lighting-App-SBSFU?