You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#30770 added some code that assumes that the check-in recipient is the entity that will communicate with the user to let them know how to put the ICD into active mode if the user needs it in active mode "now".
This is not a valid assumption; these can generally be different entities.
What probably makes the most sense is making sure that during commissioning the hint information is communicated to the SDK client; they can then decide how and whether to store it and what entities should have it. But having it stored along with the check-in key on the check-in recipient does not really make sense.
Bug prevalence
Always
GitHub hash of the SDK that was being used
master
Platform
core
Platform Version(s)
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered:
During commissioning, we get the hint information and tell application, then application needs to store them in some sort of storage in the entity that actual need to communicate with ICD device.
Reproduction steps
#30770 added some code that assumes that the check-in recipient is the entity that will communicate with the user to let them know how to put the ICD into active mode if the user needs it in active mode "now".
This is not a valid assumption; these can generally be different entities.
What probably makes the most sense is making sure that during commissioning the hint information is communicated to the SDK client; they can then decide how and whether to store it and what entities should have it. But having it stored along with the check-in key on the check-in recipient does not really make sense.
Bug prevalence
Always
GitHub hash of the SDK that was being used
master
Platform
core
Platform Version(s)
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: