* Don't attempt to send a message unless we've successfully built a deveice-messages
* Only process message exception when we're done with retries.
// FREEBIE
After provisioning a desktop client, you'll see messages sent from your
phone appear on your desktop client, and messages sent from the desktop
client appear on your phone.
* In the process extracted some of the Attachment processing logic out
of the giant MessagesManager.
* Some nullability annotations on affected files.
// FREEBIE
* new protobufs from libsignal-service-java@a1c93edc40e3ce201fa4e70339a3e6f4e197e319
* Makefile to build ObjC classes from *.proto
* refactored some touched code to minimize duplication
* removed unused protos
* deleted some dead code
* renamed method for clarity
// FREEBIE
In theory, this should have already been handled by the
YapDatabaseRelationship extension via edges.
However, in practice, there were situations (cause unknown) where
interactions would exist without an edge to their corresponding thread.
Rather than being clever with the edge/callback machinery, now threads
explicitly delete all their interactions, and interactions delete all
their attachments (when applicable).
Also, a class to clean up spurious interactions / attachments
In the process:
- refactored TSYapDatabaseObject init to specify designated initializer
- added some testing niceties to TSYapDatabaseObject
// FREEBIE
- log errors
- forward declare where possible
- clang-format
- remove inaccurate file headers
- include Pods in Example app build target to get SignalServiceKit warnings
- Fix those warnings!
// FREEBIE
Using description in log output crashes when the description is a media
message, since printing media description uses a transaction within our
existing transaction.
Instead we'll use a simpler debugDescription for simple text building,
like logging.
// FREEBIE
* fix thread preview when deleting last message
because we are doing internal accounting of what our "last" message id
is, when we delete the last message, other things get out of whack.
Caching is hard, don't do it! We can efficiently get the last object
using our existing Yap DB view.
//FREEBIE
* remove lastMessageId in favor of lastMessage for cleaner code
//FREEBIE
