Update conversation view title when group name changes.

// FREEBIE

Signal/src/Models/TSMessageAdapaters/TSMessageAdapter.m

@@ -182,7 +182,9 @@
             // repurposing call display for info message stuff for group updates, ! adapter will know because the date
             // is nil.
             //
-            // TODO: This doesn't seem like a good idea.
+            // TODO: I suspect that we'll want a separate model
+            //       that conforms to <OWSMessageData> for info
+            //       messages.
             CallStatus status = 0;
             if (adapter.infoMessageType == TSInfoMessageTypeGroupQuit) {
                 status = kGroupUpdateLeft;

Signal/src/view controllers/MessagesViewController.m

@@ -2083,14 +2083,11 @@ typedef enum : NSUInteger {
     // Currently, we update thread and message state every time
     // the database is modified.  That doesn't seem optimal, but
     // in practice it's efficient enough.
-    //
-    // 
-    dispatch_async(dispatch_get_main_queue(), ^{
-        [self updateContents];
-    });
-}
 
-- (void)updateContents {
+    // We need to `beginLongLivedReadTransaction` before we update our
+    // models in order to jump to the most recent commit.
+    NSArray *notifications = [self.uiDatabaseConnection beginLongLivedReadTransaction];
+
     [self updateBackButtonAsync];
 
     if (isGroupConversation) {
@@ -2104,8 +2101,6 @@ typedef enum : NSUInteger {
         [self setNavigationTitle];
     }
 
-    NSArray *notifications = [self.uiDatabaseConnection beginLongLivedReadTransaction];
-
     if (![[self.uiDatabaseConnection ext:TSMessageDatabaseViewExtensionName]
             hasChangesForNotifications:notifications]) {
         [self.uiDatabaseConnection readWithBlock:^(YapDatabaseReadTransaction *transaction) {