-
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
Matter.framework should make sure that MTRErrorHolder conforms to NSSecureCoding #22388
Labels
Comments
Resolved with: #22328 |
bzbarsky-apple
added a commit
to bzbarsky-apple/connectedhomeip
that referenced
this issue
Feb 18, 2023
Otherwise the errors we create cannot be usefully encoded/decoded. Fixes project-chip#22388
bzbarsky-apple
added a commit
to bzbarsky-apple/connectedhomeip
that referenced
this issue
Feb 20, 2023
Otherwise the errors we create cannot be usefully encoded/decoded. Fixes project-chip#22388
bzbarsky-apple
added a commit
that referenced
this issue
Feb 21, 2023
Otherwise the errors we create cannot be usefully encoded/decoded. Fixes #22388
kkasperczyk-no
pushed a commit
to kkasperczyk-no/sdk-connectedhomeip
that referenced
this issue
Mar 15, 2023
Otherwise the errors we create cannot be usefully encoded/decoded. Fixes project-chip/connectedhomeip#22388
kkasperczyk-no
pushed a commit
to kkasperczyk-no/sdk-connectedhomeip
that referenced
this issue
Mar 15, 2023
Otherwise the errors we create cannot be usefully encoded/decoded. Fixes project-chip/connectedhomeip#22388
lecndav
pushed a commit
to lecndav/connectedhomeip
that referenced
this issue
Mar 22, 2023
…-chip#25201) Otherwise the errors we create cannot be usefully encoded/decoded. Fixes project-chip#22388
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem
MTRErrorHolder does not conforms to NSSecureCoding which makes it difficult to be sent over XPC. We have seen a few crashes because of this.
Proposed Solution
Make sure that MTRErrorHolder conforms to NSSecureCoding
The text was updated successfully, but these errors were encountered: