{"version":"2.1.233","anchor":"remote-session-control-requests-go-through-one-dispatch-obje","canonical_anchor":"remote-session-control-requests-go-through-one-dispatch-obje","heading":"Remote session control requests go through one dispatch object","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233\/e\/remote-session-control-requests-go-through-one-dispatch-obje","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233","markdown":"### Remote session control requests go through one dispatch object\n\nRemote permission prompts and dialogs now route through one dispatch-and-cancel object.\n\n**What**\n\nPermission prompts and user dialogs raised during a remote session now go through a single dispatch-and-cancel object instead of separate callbacks. Whether anything about the behaviour changes for a user is not settled by the code; the request and cancel paths look equivalent.\n\n**Evidence**\n\n`[useRemoteSession] User dialog request cancelled: `\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}