gmail.get.selected_emails_data() returns wrong emails
See original GitHub issueI recently noticed when gmail.get.selected_emails_data()
is called (and emails are selected) the wrong emails are returned. When viewing the “Primary” inbox tab, it seems to be returning emails from either “Social” or “Promotions” of the same index number.
Tried to debug a little and it seems gmail.helper.get.visible_emails_pre()
is returning this URL:
https://mail.google.com/mail/u/0/?ui=2&ik=b92f69409f&rid=undefined&view=tl&num=120&rt=1&start=NaN&sstart=NaN&search=inbox
Requests to this URL seems to be returning emails from the “Social” and “Promotions” tabs.
Could the rid=undefined
and start=NaN&sstart=NaN
be causing the problem? Let me know what info you need from me to help resolve the issue. Thanks!
Issue Analytics
- State:
- Created 6 years ago
- Comments:16 (2 by maintainers)
Top Results From Across the Web
Getting someone else's mail - Gmail Help - Google Support
If you get someone else's mail, check the reasons below to get help. If the sender added dots to your address, you'll still...
Read more >Change Your Display Name in Gmail - OIT Service Center
In your Settings, go to the Accounts tab. Where it says Send Mail As:, click the edit info link next to the account...
Read more >Resolve errors | Gmail - Google Developers
This guide provides instructions on how to resolve specific API errors. Resolve a 400 error: Bad request. This error might result from these...
Read more >How to Fix Gmail When Its Not Receiving Emails - YouTube
Sign in on your Gmail account, with your email and password. 2. ... If you find any issue in your filter, then select...
Read more >Gmail - Free Storage and Email from Google
Activity includes accessing the product or its content at least every 2 years. We may take action on inactive accounts, which may include...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hi @josteink, sorry for not getting back to you. I finally had some time to get back to the project that uses this. I tested your fix and unfortunately it does not work for me. It works fine for “@gmail.com” addresses, but not my enterprise Gmail account with a custom domain name.
Using “search=mbox” works for both my “@gmail.com” account and enterprise account. I’ll see if I can get some of my beta testers to give me feedback on this and get a larger sample size.
Thanks for your help on this.
mbox is a unix plain-text file-format for local mail-agents like pine and mutt to organize email.
It’s an interesting theory, but I’m absolutely positive that it is not related to anything happening in the Gmail web front-end.
@scottwrobinson: Sorry about the hold up. If you’re still around…
Based on @Banjerr’s PR you linked to, the comment says:
If we can determine whether we are a enterprise/apps-account or regular gmail account, we should use that to determine the best value.
It seems, we should use “inbox” for enterprise accounts and “mbox” for regular gmail accounts.
Could you bother preparing a PR with those changes, and I will do some testing on my end. if everything works here for me too, I’d be happy to merge.
(And if it causes regressions, we’ll just take it from there)