A bad crossSessionInbound value now gives you a settings error instead of passing silently.
What's wrong with this entry?
An unacceptable crossSessionInbound value now produces its own settings error rather than passing silently, and a further check on the same setting can also mark the file invalid.
"crossSessionInbound"
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.225
Held peer messages now say which settings tier held them
Both mention cross inbound
-
v2.1.224
Cross-session messages from a coordinator are now delivered by default
Both mention cross inbound
-
v2.1.234
Messages injected by a host are classified separately from peer messages
Both mention cross