Move WiFi association processing to Rendezvous StateMachine #3019
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.
Problem
As part of Rendezvous state machine, the controller sends network (e.g. WiFi) credentials to the device. Currently, the controller propagates a Rendezvous message from device to the controller app (e.g. CHIP Tool iOS app), which triggers the app to collect the credentials from the user. The app constructs another Rendezvous message containing the credentials and sends it to the device.
This puts extra burden on the app to understand the Rendezvous message structure. Instead, the Rendezvous state machine should process the message, and call the delegate registered by app to collect the WiFi credentials. Also, the state machine should construct the required Rendezvous message and send it to the device.
Summary of Changes
Fixes #2818