- Shipped
- 30 ஆகஸ்ட், 2026 அன்று 1:03 AM UTC
- Author
- Kamo
- Commit
- 3374236
VoipService now answers an unprovisioned account with 409 and both a machine code (`error`) and a sentence a member can act on (`message`). apiCall read `error` first, so the code would have gone on screen and the explanation been thrown away; it prefers `message` now, which is also the order the mobile client already reads them in. SmsNewConversation showed one blanket string for every failure. "Check the number and try again" is actively misleading when the member's own account has no number to text FROM: there is nothing to check and no way out of the loop. It shows the server's words when it has them, and keeps the blanket message for anything that is only a code.