{"version":"2.1.280","anchor":"device-linking-qrpairing-requests-can-carry-an-onupload-c","canonical_anchor":"device-linking-qrpairing-requests-can-carry-an-onupload-c","heading":"Device-linking (QR\/pairing) requests can carry an onUpload callback","tier":"internal","area":"Device Linking","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/device-linking-qrpairing-requests-can-carry-an-onupload-c","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Device-linking (QR\/pairing) requests can carry an onUpload callback\n\nDevice-linking (QR pairing) requests can now carry an onUpload callback\n\n**Unclear.** What triggers the onUpload callback or what it's used for is not stated in the finding.\n\n**What**\n\nThe tracker used for device-linking requests, such as pairing a new device via QR code, now accepts and stores an `onUpload` callback in addition to the existing `kind`, `accepts`, and `instanceId` fields when tracking a live request.\n\n**Why**\n\nThis lets the pairing flow run additional logic when something is uploaded as part of linking a device, though the finding doesn't specify what that upload step does.\n\n- Area: Device Linking\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}