Wrong thread Id when replying to a conversation in the new Gmail UI

[bjo...@cirruspath.com]

Hi. I have a question about using InboxSDK with the upcoming Gmail UI changes. I've noticed that when I reply to a message in a thread the wrong thread id is being returned from getThreadId(). The thread id returned is always the thread id of the first message.

I've included a screenshot of the XHR request (wrong-thread-id.png) that shows the response when the message is sent. You can see that the threadId returned is 1622069bd2aef98d but I was expecting the thread Id to be 162206a0873a52b9. After the message is sent I can inspect the DOM and see that Google has 162206a0873a52b9 as the data-legacy-message-id attribute (correct-thread-in-dom.png).

This works fine in the  current Gmail UI and is only a problem with the new Gmail UI.

        sdk.Compose.registerComposeViewHandler(composeView => {

            composeView.on('sent', event => {

                $q.all([event.getMessageID(), event.getThreadID()])

                    .then(result => {

                        let messageId = result[0];

                        let threadId = result[1];

                        console.log('*** messageId', messageId);

                        console.log('*** threadId', threadId);

                    });

            });

        });

[Aleem Mawani]

Thanks for the detailed report, we'll be taking a look at this today.

ᐧ

--
You received this message because you are subscribed to the Google Groups "InboxSDK" group.
To unsubscribe from this group and stop receiving emails from it, send an email to inboxsdk+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/inboxsdk/4f4b5b70-4a23-4c16-8cdd-3112c673d63a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[bjo...@cirruspath.com]

I should point out that it's the message id that is wrong not the thread id. The message id should be the message id of the message that was just sent. Instead InboxSDK getMessageId() is always returning the message id of the first message in the thread (which is the same as the thread id).

[Omar Ismail]

This issue is now fixed. Thanks for the bug report!

ᐧ

--

You received this message because you are subscribed to the Google Groups "InboxSDK" group.
To unsubscribe from this group and stop receiving emails from it, send an email to inboxsdk+u...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/inboxsdk/c7294708-feee-4b99-bc37-1a245c3c7273%40googlegroups.com.

[Yoni Bazak]

Hi,

I hope I in the right subject.

I just wonder how I can locate the thread id in the new gmail links

Old gmail is very easy:  https://mail.google.com/mail/u/0/#inbox/1630209116a3af45 and thread id is: 1630209116a3af45 

In the new gmail same thread link is: https://mail.google.com/mail/u/0/?zx=3xcdey2cogvc#inbox/FMfcgxmZVPbZvwJWCvBMvjxglSMPvsvW and is no option to find it

I also find the source of the page and the thread id is not there

I also try to find in the "show original" option, but I can find only the message id, and it not help

How can I locate the thread id in new gmail

[Omar Ismail]

Use the SDK to get the thread id :)

ᐧ

To view this discussion on the web visit https://groups.google.com/d/msgid/inboxsdk/016c5efd-382b-4f20-9558-09624a017dfa%40googlegroups.com.

[Yoni Bazak]

My qustion is how I can locate the thread id by using the url or similar way, not by using software

Thanks!!

[Omar Ismail]

If you pop out the thread into a separate window then the new window will have the thread id in the address bar. Note, this url is the new "sync" style id and doesn't yet work with the Gmail API.

ᐧ

To view this discussion on the web visit https://groups.google.com/d/msgid/inboxsdk/f21079da-7c24-4dcd-8e87-0fa6a2618d01%40googlegroups.com.

[Yoni Bazak]

Thanks Omar.

This is any option to snooze emails via Gmail API?
Thanks

Yoni Bazak CTO at QuietLife Technologies A  9 Bet Hadfus St, Jerusalem IL P  972.2.996.3388  E  yo...@quietlife.tech  W  http://quietlife.tech

[Omar Ismail]

Not that I know of.

ᐧ

[Yoni Bazak]

This is any plan to add it?

Yoni Bazak CTO at QuietLife Technologies A  9 Bet Hadfus St, Jerusalem IL P  972.2.996.3388  E  yo...@quietlife.tech  W  http://quietlife.tech

[Yoni Bazak]

Hi Omar, this is any plan to add snooze to the sdk?

Thanks

Yoni Bazak CTO at QuietLife Technologies A  9 Bet Hadfus St, Jerusalem IL P  972.2.996.3388  E  yo...@quietlife.tech  W  http://quietlife.tech

[Aleem Mawani]

At the moment there are no plans to do this.

ᐧ

To view this discussion on the web visit https://groups.google.com/d/msgid/inboxsdk/CA%2BGvCX1cZEVPkq7LnLkJk42bUQptuHqbC4P_F06%3DwObm4emDOw%40mail.gmail.com.

[Rodney Kuhn]

Hi Omar,

Thank you for the great work you and the team have been doing.  InboxSDK is truly amazing!

I was wondering if is possible to retrieve the able to new "sync" style id that you refer to, through InboxSDK?  Or if not, could you perhaps recommend that you could find such an id?  I'm also interested know if you know if Gmail plans to support opening a thread via the URL (with the thread-id appended).  One of their recent documents seemed to suggest it may not be around for much longer. 

I guess the more developers that require this, the better the chances that this feature might stay in.

Best regards,

Rod

[Jared Sohn]

I'm wondering if there was a regression for this bug? I think we're experiencing something similar. Our scenario is that when we send a draft, getMessageID() returns the message id from before it was sent (which matches the thread id) instead of the message id for the sent message. This happens only in the new gmail UI for us as well.

[Jared Sohn]

Bumping this. Let me know if you need more information to check this (but I think the original post from this thread may have sufficient information.)