Wait for Max PIN length before generating credentials #2260
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Type of Change
Checklist
Description of Change
This change fixes a bug where if the handler for
RequirePINforRemoteOperation
runs before themaxCodeLength
attribute of thelockCodes
capability is set, a default pin length of 4 would be used, which may be shorter than the minimum pin length of the device specified by theMinPINCodeLength
attribute. Therefore, the read was removed frominit
andadded
, and was moved to the handler forMaxPINCodeLength
to guarantee that the max pin length is known before attempting to generate the COTA credential.Summary of Completed Tests
Updated UTs and tested on device.