-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updating the Fabric Label from iOS CHIPTool results in an error but updates the label correctly #15114
Comments
bzbarsky-apple
added a commit
to bzbarsky-apple/connectedhomeip
that referenced
this issue
Feb 12, 2022
1. Send a NOCResponse instead of a status response, like the spec says. 2. Implement the "check for fabric label collision" bit from the spec. 3. Update the name of the "Fabrics" attribute to match the spec. 4. Add a test for UpdateFabricLabel and reading the Fabrics attribute both before and after updating the label. Fixes project-chip#15114
bzbarsky-apple
added a commit
to bzbarsky-apple/connectedhomeip
that referenced
this issue
Feb 12, 2022
1. Send a NOCResponse instead of a status response, like the spec says. 2. Implement the "check for fabric label collision" bit from the spec. 3. Update the name of the "Fabrics" attribute to match the spec. 4. Add a test for UpdateFabricLabel and reading the Fabrics attribute both before and after updating the label. Fixes project-chip#15114
bzbarsky-apple
added a commit
to bzbarsky-apple/connectedhomeip
that referenced
this issue
Feb 12, 2022
1. Send a NOCResponse instead of a status response, like the spec says. 2. Implement the "check for fabric label collision" bit from the spec. 3. Update the name of the "Fabrics" attribute to match the spec. 4. Add a test for UpdateFabricLabel and reading the Fabrics attribute both before and after updating the label. Fixes project-chip#15114
vivien-apple
pushed a commit
that referenced
this issue
Feb 12, 2022
* Fix responses for UpdateFabricLabel to match the spec. 1. Send a NOCResponse instead of a status response, like the spec says. 2. Implement the "check for fabric label collision" bit from the spec. 3. Update the name of the "Fabrics" attribute to match the spec. 4. Add a test for UpdateFabricLabel and reading the Fabrics attribute both before and after updating the label. Fixes #15114 * Fix handling of chip_tests_variables_has inside #each. It looks like #each breaks the .parent chain that chip_tests_variables_has relies on. Just manually hook that up.
jamesluo11
pushed a commit
to jamesluo11/connectedhomeip
that referenced
this issue
Apr 26, 2022
…15122) * Fix responses for UpdateFabricLabel to match the spec. 1. Send a NOCResponse instead of a status response, like the spec says. 2. Implement the "check for fabric label collision" bit from the spec. 3. Update the name of the "Fabrics" attribute to match the spec. 4. Add a test for UpdateFabricLabel and reading the Fabrics attribute both before and after updating the label. Fixes project-chip#15114 * Fix handling of chip_tests_variables_has inside #each. It looks like #each breaks the .parent chain that chip_tests_variables_has relies on. Just manually hook that up.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem
Using the Fabric Management screen to update the Fabric Label results in an error.
The label does in fact get updated correctly as visiting the same page again will show the correct label for the fabric.
all-clusters-app logs
Proposed Solution
Debug and fix 🤷
The text was updated successfully, but these errors were encountered: