What changed
The private-message composer now becomes available correctly if you open a different conversation while an earlier send is still waiting for its reply. When that send finishes, the currently open thread refreshes its controls.
Why it matters
Previously, the first message could save successfully while the other conversation’s text field and Send button stayed disabled. You could see the conversation but could not continue writing there without reopening it or waiting for another refresh.
For example, send a message to one ally, use Back, and open another conversation before the first send finishes. Once that send has finished, the second conversation’s composer becomes available. A new reply goes to the conversation currently shown, and the original message stays with its original recipient.
Next time you play
You can move between your private conversations while a send is waiting. On short landscape screens, use Back to return to the conversation list. After the pending send finishes, continue writing in the selected thread. Existing message-request acceptance, blocking restrictions and the three-second send cooldown still apply.


