Under the hood
Useful1 Signal2
Resume, remote sessions and several other paths now get an explicit storage handle instead of a global.
What's wrong with this entry?
Anonymous. No account, no email.
What
Session resume and lookup, the fullscreen boot check, remote session creation, background and remote agent resume, login profile saving, the SDK stream transport and the upsell notification path now all take an explicit storage handle instead of reaching for a global. This decides which storage backend each operation writes to, not what it does.
Details
- Remote session creation also sends the storage handle and a
settings_gatetelemetry field.
Evidence
storageV5
Strings lifted out of the shipped bundle, so the claim above can be checked against them.