You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
Bug FixesKind: in v2.1.278,
Bug FixesSection of the release
What
In 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.
Why
This 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.
