zap configure tool edits unintended Clusters about zap HOT 3 CLOSED

@brdandu , @jingteng25742 : can some of you test this and see if it's still happening?

from zap.

I followed the above reproducer steps. In step 2 I could not find configure.sh so I ran run_zaptool.sh and then opened the all-clusters-app.zap file. I could not find any OTA clusters enabled on Endpoint 1 but saw "OTA Software Update Requestor" server side cluster on Endpoint 0. I disabled the same and the only diff in the zap file I see is as follows:

--- a/examples/all-clusters-app/all-clusters-common/all-clusters-app.zap
+++ b/examples/all-clusters-app/all-clusters-common/all-clusters-app.zap
@@ -1516,7 +1516,7 @@
"mfgCode": null,
"define": "OTA_REQUESTOR_CLUSTER",
"side": "server",

•      "enabled": 1,
  

•      "enabled": 0,
       "commands": [],
       "attributes": [
         {
  

I believe the issue has been resolved.

from zap.

This has been resolved a while back.

from zap.