No sent event if I started to compose a new email and entered the email address to the letter during 5 seconds after the last send

[Fyodor P]

Usually, I can get PRESENDING event and then SENT event inside sdk.Compose.registerComposeViewHandler.

But if after I sent the email I will compose a new one and enter the email address to it in 5 seconds I will get SENT event with threadId from the previous email before sending the current. 

And after sending the new email I will not get SENT event for it.

Screenshots:

1 - After sending the first letter

2 - After creating a new letter and entering an email address in 5 seconds

3 - After sending the second letter

[Ali Shah]

Hi I'm actually getting this exact same issue. I've tried everything, cancelling out listeners in the hopes of flushing out events, but nothing seems to resolve it. It's easily reproducible, but not on every single send. But for sure it will always happen at least once in a batch of 10 emails. So sending 10 emails in sequence and logging in presending and sent event listeners will demonstrate at least one case in which:
- sent fires BEFORE presending and carries the previous email's threadId, but the current emails messageId

- presending then fires afterwards (any mutations to the message do update the current message, not the message with the previous threadId that's logging)
- no sent event is fired with any updated threadId afterwards.

It's reproducible in box the old inboxSDK script and in the new npm package.

This is affecting our released chrome ext and resulting in a considering inflow of customer complaints and tickets :(

[Silvio Henrique Ferreira]

I can also reproduce this.

It happens to me in 100% of cases by doing the following:

 - Create two new messages

 - Set the recipient, subject to the first
 - Send the first message
 - Quickly fill the recipient or subject of the second message, but don't send it, let the draft save (about 5 to 10 seconds, but sometimes up to 40s)

 - The "sent" event is triggered for the second message when it is saved as a draft

When the second message is REALLY sent, I don't get a "sent" event anymore.

I had partial success by using the "destroy" method, which gives me access to the draft ID.

I have to get the final messageID using the Gmail API, but with a caveat:

I have to wait about 5-10 seconds to query the API, otherwise I get an incorrect messageID (it doesn't belong to the previous message either).

[Asfandyar Malik]

Did anyone fix this ? 

[Ali Shah]

I received an update to the related github issue yesterday that the fix is pushed out. In my testing so far the issue does indeed seem to be resolved