What is the messageId that InboxSDK returns when in Google Inbox?

[do...@swoot.com]

I'm a bit puzzled on this one. When in the context of Google Inbox, if you call messageView.getMessageIDAsync(), you'll get a hex value that looks like a gmail message id, but doesn't seem to work anywhere you'd actually use that id. For example, sending that value to https://www.googleapis.com/gmail/v1/users/me/messages/${id} returns a 404.

Anyone know what you can actually do with that id value? In the InboxSDK docs, that method is marked as having Inbox support, so I figure those strings must be good for something.

[Chris Cowan]

Heh, you've stumbled onto the issue I've been working on for the past few days. Currently the SDK reports an incorrect ID for threads and messages sent from the signed-in user within Inbox. A fix should be going out for that today or early next week. (In Inbox, we can decode the correct ID for most threads and messages from the attributes of the DOM element. But it turns out that the ID in the attributes for threads and messages sent from the signed-in user in Inbox don't match up with the IDs in the Gmail API. It seems we can make http requests to certain Inbox/Google endpoints to translate this bad Inbox ID into a good ID that matches up with Gmail API, and I'm working on making the SDK do that when you call getMessageIDAsync.)

[Chris Cowan]

The fix for this issue in Inbox is live now.

[Doug Keen]

Awesome. Thanks for the fast turnaround.

--
You received this message because you are subscribed to a topic in the Google Groups "InboxSDK" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/inboxsdk/yPMR6Ty07sE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to inboxsdk+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/inboxsdk/25e2112d-f7a5-4dcc-96a8-c8d6de90b627%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Garret Heaton]

Thanks for this, Chris. In my initial testing, getMessageIDAsync() works well except in one case:

In Inbox, viewing (sdk.Conversations.registerMessageViewHandler) a reply sent by me to a thread/conversation (like this one). The ID returned in this case is different than the one returned by getMessageID(), but neither is valid.

Cases I've tested where getMessageIDAsync() does work:

- In Gmail: Viewing any message (even if it is one that did not work in Inbox)

- In Inbox: Viewing any message sent by someone else

- In Inbox: Viewing the first message in a thread/conversation that I sent

- In Inbox: Viewing a reply sent by me from Gmail (logged into the same account)

By "works", I mean that the ID returned can be used in the Gmail HTTP API to fetch message data.

getThreadIDAsync() also seems to work correctly in all cases.

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/CAMbE7mey4uquhLZ8ZEeuefGocYD-CuQv40048rFG%3D0FD5w05Tw%40mail.gmail.com.

[Chris Cowan]

Thanks for reporting that. It looks like that after an email is synced to Inbox/Gmail but before it is actually sent as an email it has a different ID. (If you run getMessageIDAsync() on the message as soon as it shows up, then we get that temporary ID and cache it.) This issue is especially important to us as it seems to overlap with our goal of getting the message ID resulting from hitting send in a composeview, so hopefully we'll have some progress on this to report within a week.

On Monday, June 19, 2017 at 11:17:56 AM UTC-7, Garret Heaton wrote:

Thanks for this, Chris. In my initial testing, getMessageIDAsync() works well except in one case:

In Inbox, viewing (sdk.Conversations.registerMessageViewHandler) a reply sent by me to a thread/conversation (like this one). The ID returned in this case is different than the one returned by getMessageID(), but neither is valid.

Cases I've tested where getMessageIDAsync() does work:

- In Gmail: Viewing any message (even if it is one that did not work in Inbox)

- In Inbox: Viewing any message sent by someone else

- In Inbox: Viewing the first message in a thread/conversation that I sent

- In Inbox: Viewing a reply sent by me from Gmail (logged into the same account)

By "works", I mean that the ID returned can be used in the Gmail HTTP API to fetch message data.

getThreadIDAsync() also seems to work correctly in all cases.

On Sat, Jun 17, 2017 at 7:16 AM Doug Keen <do...@swoot.com> wrote:

Awesome. Thanks for the fast turnaround.

On Fri, Jun 16, 2017, 7:02 PM Chris Cowan <co...@streak.com> wrote:

The fix for this issue in Inbox is live now.

On Friday, June 16, 2017 at 1:11:57 PM UTC-7, Chris Cowan wrote:

Heh, you've stumbled onto the issue I've been working on for the past few days. Currently the SDK reports an incorrect ID for threads and messages sent from the signed-in user within Inbox. A fix should be going out for that today or early next week. (In Inbox, we can decode the correct ID for most threads and messages from the attributes of the DOM element. But it turns out that the ID in the attributes for threads and messages sent from the signed-in user in Inbox don't match up with the IDs in the Gmail API. It seems we can make http requests to certain Inbox/Google endpoints to translate this bad Inbox ID into a good ID that matches up with Gmail API, and I'm working on making the SDK do that when you call getMessageIDAsync.)

On Friday, June 16, 2017 at 12:54:16 PM UTC-7, do...@swoot.com wrote:

I'm a bit puzzled on this one. When in the context of Google Inbox, if you call messageView.getMessageIDAsync(), you'll get a hex value that looks like a gmail message id, but doesn't seem to work anywhere you'd actually use that id. For example, sending that value to https://www.googleapis.com/gmail/v1/users/me/messages/${id} returns a 404.

Anyone know what you can actually do with that id value? In the InboxSDK docs, that method is marked as having Inbox support, so I figure those strings must be good for something.

--

You received this message because you are subscribed to a topic in the Google Groups "InboxSDK" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/inboxsdk/yPMR6Ty07sE/unsubscribe.

To unsubscribe from this group and all its topics, send an email to inboxsdk+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/inboxsdk/25e2112d-f7a5-4dcc-96a8-c8d6de90b627%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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+unsubscribe@googlegroups.com.

[Garret Heaton]

Thanks, that makes sense. I can confirm that with a clear InboxSDK cache the proper IDs are returned for not-just-sent messages.

We have seen similar timing specific behavior when looking at the "View original" page for a message immediately after it is synced to Inbox/Gmail. The Message-ID header will be inaccurate for a short time until the message is actually sent.

Looking forward to a working send event from the ComposeView as well.

On Mon, Jun 19, 2017 at 6:10 PM, Chris Cowan <co...@streak.com> wrote:

Thanks for reporting that. It looks like that after an email is synced to Inbox/Gmail but before it is actually sent as an email it has a different ID. (If you run getMessageIDAsync() on the message as soon as it shows up, then we get that temporary ID and cache it.) This issue is especially important to us as it seems to overlap with our goal of getting the message ID resulting from hitting send in a composeview, so hopefully we'll have some progress on this to report within a week.

On Monday, June 19, 2017 at 11:17:56 AM UTC-7, Garret Heaton wrote:

Thanks for this, Chris. In my initial testing, getMessageIDAsync() works well except in one case:

In Inbox, viewing (sdk.Conversations.registerMessageViewHandler) a reply sent by me to a thread/conversation (like this one). The ID returned in this case is different than the one returned by getMessageID(), but neither is valid.

Cases I've tested where getMessageIDAsync() does work:

- In Gmail: Viewing any message (even if it is one that did not work in Inbox)

- In Inbox: Viewing any message sent by someone else

- In Inbox: Viewing the first message in a thread/conversation that I sent

- In Inbox: Viewing a reply sent by me from Gmail (logged into the same account)

By "works", I mean that the ID returned can be used in the Gmail HTTP API to fetch message data.

getThreadIDAsync() also seems to work correctly in all cases.

On Sat, Jun 17, 2017 at 7:16 AM Doug Keen <do...@swoot.com> wrote:

Awesome. Thanks for the fast turnaround.

On Fri, Jun 16, 2017, 7:02 PM Chris Cowan <co...@streak.com> wrote:

The fix for this issue in Inbox is live now.

On Friday, June 16, 2017 at 1:11:57 PM UTC-7, Chris Cowan wrote:

Heh, you've stumbled onto the issue I've been working on for the past few days. Currently the SDK reports an incorrect ID for threads and messages sent from the signed-in user within Inbox. A fix should be going out for that today or early next week. (In Inbox, we can decode the correct ID for most threads and messages from the attributes of the DOM element. But it turns out that the ID in the attributes for threads and messages sent from the signed-in user in Inbox don't match up with the IDs in the Gmail API. It seems we can make http requests to certain Inbox/Google endpoints to translate this bad Inbox ID into a good ID that matches up with Gmail API, and I'm working on making the SDK do that when you call getMessageIDAsync.)

On Friday, June 16, 2017 at 12:54:16 PM UTC-7, do...@swoot.com wrote:

I'm a bit puzzled on this one. When in the context of Google Inbox, if you call messageView.getMessageIDAsync(), you'll get a hex value that looks like a gmail message id, but doesn't seem to work anywhere you'd actually use that id. For example, sending that value to https://www.googleapis.com/gmail/v1/users/me/messages/${id} returns a 404.

Anyone know what you can actually do with that id value? In the InboxSDK docs, that method is marked as having Inbox support, so I figure those strings must be good for something.

--

You received this message because you are subscribed to a topic in the Google Groups "InboxSDK" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/inboxsdk/yPMR6Ty07sE/unsubscribe.

To unsubscribe from this group and all its topics, send an email to inboxsdk+u...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/inboxsdk/25e2112d-f7a5-4dcc-96a8-c8d6de90b627%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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/CAMbE7mey4uquhLZ8ZEeuefGocYD-CuQv40048rFG%3D0FD5w05Tw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--

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/2a770dce-1452-4223-aa88-27489f5ec235%40googlegroups.com.

[Chris Cowan]

We've fixed the issue of messageView.getMessageIDAsync() returning an incorrect id for just-sent messages in Inbox, and made the SDK clear its old cache so no old incorrect cached values will be returned. In other news, we expect to have the ComposeView sent event supported in Inbox within a few days.

To unsubscribe from this group and all its topics, send an email to inboxsdk+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/inboxsdk/25e2112d-f7a5-4dcc-96a8-c8d6de90b627%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/inboxsdk/CAMbE7mey4uquhLZ8ZEeuefGocYD-CuQv40048rFG%3D0FD5w05Tw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
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+unsubscribe@googlegroups.com.