{"version":"2.1.296","anchor":"permission-handling-for-updatedpermissions-in-bridge-replies","canonical_anchor":"permission-handling-for-updatedpermissions-in-bridge-replies","heading":"Bad permission updates from connected apps now go through shared handling","tier":"internal","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/permission-handling-for-updatedpermissions-in-bridge-replies","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Bad permission updates from connected apps now go through shared handling\n\nMalformed `updatedPermissions` replies from a bridge client are now handled by a shared routine labelled as refusing them\n\n**Unclear.** Whether malformed permission updates from a bridge client are still simply ignored or are now refused in a way the app sees is not stated.\n\n**What**\n\nWhen another app connected to a session through the bridge answers a permission question, its reply can include `updatedPermissions`, a set of permission changes. A malformed set used to be dropped with the warning \"Malformed updatedPermissions from bridge client ignored\". It now goes through a shared routine, labelled \"refused\" and \"bridge client\". The same routine also handles permission replies that arrive for a question no longer waiting.\n\n**Why**\n\nMalformed permission updates from connected apps are now dealt with in one place. The warning text you see in logs is different.\n\n- Area: Permissions\n- Names: `updatedPermissions`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}