42c24dd098
Turns out textsecure.messaging is only set up on first connection to the server. When we start up offline, we never do that. And it prevents the user from opening every conversation. There's a whole lot more to do to bulletproof ourselves against a missing textsecure.messaging (and then beyond that, queuing outgoing messages so they don't get dropped completely when offline). Hence, it's a band-aid. |
||
|---|---|---|
| .. | ||
| blockedNumbers.js | ||
| conversations.js | ||
| messages.js | ||