Embedding programs declare which dialogs they can show; unsupported ones are left to other clients.
What's wrong with this entry?
A program embedding the cloud headless client lists the dialog kinds it can display in its initialize message, under supportedDialogKinds. Requests for an undeclared kind are not forwarded; the client prints a notice and leaves the dialog to another attached client or to the session's dialog timeout.
- Permission requests are always forwarded regardless of what the host declared.
- Skipped dialogs are counted as
dialogs_not_declaredat end of run. - The field is added to the honoured initialize options unconditionally.
its initialize did not declare the kind
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.