Create Conversation Flow - directConversationID after Delete is different than original directConversationID
In the create conversation flow, according to what is implemented on Android the following order is expected:
- Send DM message with no replyToConversationID or usernames attached.
- Use save directConversationID from response for future use.
- GET the conversation using the saved directConversationID.
- PATCH the usernames to the conversation using the saved directConversationID.
- DELETE the original status from the conversation.
- Send the original DM using the saved directConversationID in the original message as the inReplyToConversationID field.
Problems:
- The directConversationID returned from (6) is not the same as the saved directConversationID from (1).
- GETing the Conversation with the directConversationID from (6) contains 0 accounts in the accounts list even though they were PATCHed in (4).
- Using the original directConversationID from (1) to GET conversation after (6) returns an error.
This means in order to have the conversation return accounts, I need to PATCH the usernames again, but this time just send a DM using the replyToConversationID and attach the usernames. This way the message is not lost and there are users to receive the message. This makes it seem as though the original 2-5 is pointless. Why wouldn't I just send a DM, use the directConversationID to patch usernames, fetch the conversation, then send the first message?