Change Details

Ran web and mobile app locally and nothing crashes/there are no regressions. More testing of this function will come in subsequent diffs. **UPDATE** To test that the queries were returning the correct information, I logged out `row.targetMessageID.toString()` and got this result, which matched what I found in the database: {F277031} {F277032} (also note that the message content no longer has `targetMessageID`)

Ran web and mobile app locally and nothing crashes/there are no regressions. More testing of this function will come in subsequent diffs. **UPDATE** To test that the queries were returning the correct information, I logged out `row.targetMessageID.toString()` and got this result, which matched what I found in the database: {F277031} {F277032} (also note that the message content no longer has `targetMessageID`)

Ran web and mobile app locally and nothing crashes/there are no regressions. More testing of this function will come in subsequent diffs. **UPDATE** To test that the queries were returning the correct information, I logged out `row.targetMessageID.toString()` and got this result, which matched what I found in the database: {F277031} {F277032} (also note that the message content no longer has `targetMessageID`)