{"version":"2.1.278","anchor":"sdk-startup-diagnostic-message-assignment-bug-fixed","canonical_anchor":"sdk-startup-diagnostic-message-assignment-bug-fixed","heading":"SDK startup diagnostic message assignment bug fixed","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.278\/e\/sdk-startup-diagnostic-message-assignment-bug-fixed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.278","markdown":"### SDK startup diagnostic message assignment bug fixed\n\nFixed a bug where a specific SDK shutdown reason never appeared in its own diagnostic log line\n\n**What**\n\nIn the SDK's startup-exit diagnostic logging, the code path for a permanently-closed transport (the connection used to talk to the SDK) was writing its message into the wrong variable, so that reason likely never actually showed up in the printed `SDKStartup: exiting without result` diagnostic line. This has been corrected.\n\n**Why**\n\nThis means diagnostic logs for SDK shutdowns will now correctly report \"transport closed permanently\" as the reason when that's what happened, making it easier to debug why an SDK session exited.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}