Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GMail unread count stuck #1018

Closed
Cris70 opened this issue Apr 24, 2019 · 17 comments

Comments

Projects
None yet
3 participants
@Cris70
Copy link

commented Apr 24, 2019

  • Wavebox Version: 4.9.6 beta
  • Operating System & Version: linux openSUSE Tumbleweed 20190420
  • (Linux only) Install method: rpm (zypper)
  • Account type (if applicable): Gmail

Expected & actual behavior
Wavebox should show the unread count in the account badge

Steps to reproduce
Always happens

Is the bug persistent or intermittent?
Persistent

Screenshots
image

Additional information
Unread count is stuck at 6 (see screenshot) even though I have no unread email. Reload, resync, reauthenticate... all are ineffective. Unread count even stays across reboots.

@nmat

This comment has been minimized.

Copy link
Contributor

commented Apr 25, 2019

@Cris70 there is a knowledge base about the unread count on the main website.

https://wavebox.io/kb/gmail-inbox-type

Please check that to see if it helps with the unread counts

@Cris70

This comment has been minimized.

Copy link
Author

commented Apr 25, 2019

Hi @nmat and thank you for your reply. Unfortunately the problem here is quite different: the read count is not only wrong, it is completely stuck. I mean, it's always at 6.
Even if I get new messages, the unread count does not increase. When I read them, it does not decrease.
BTW I have checked out the KB and verified that the inbox type is in sync between the gmail configuration and Wavebox's.

@Thomas101

This comment has been minimized.

Copy link
Member

commented Apr 29, 2019

@Cris70 which Inbox type are you using in Gmail & Wavebox? If you're using the Default Inbox type in Gmail, which Categories do you have enabled?

@Cris70

This comment has been minimized.

Copy link
Author

commented Apr 29, 2019

@Thomas101 I am using default inbox type with all five categories enabled.

@Thomas101

This comment has been minimized.

Copy link
Member

commented Apr 30, 2019

Thanks! There are a couple of other quick things that might clear it...

  • If you click on the Tray Icon and use the menu's to navigate to your Gmail account, does clicking through any of the emails clear the count at all or does it still remain stuck?
  • I know you've re-authenticated the account, but if you add it a second time and set it to Default Inbox as well does that show a different count, or still stuck on the 6?
@Cris70

This comment has been minimized.

Copy link
Author

commented May 1, 2019

Hi @Thomas101

  • If you click on the Tray Icon and use the menu's to navigate to your Gmail account, does clicking through any of the emails clear the count at all or does it still remain stuck?

This is where it gets even weirder: both the tray icon and the mini-window show the number 6, but then they do not show any message. See the screenshots:
image

image

  • I know you've re-authenticated the account, but if you add it a second time and set it to Default Inbox as well does that show a different count, or still stuck on the 6?

I'm not sure I understand correctly here. Do you want me to add my google account to Wavebox a second time? Is it even possible?

Cris

@Thomas101

This comment has been minimized.

Copy link
Member

commented May 2, 2019

Thanks for sending the info! I have to be honest, I wasn't expecting that at all. My initial suspicion is that the feed is returning something that we're not expecting. It would be great to get an eye on that. The current logging stack is a little weak here, but you should be able to get an idea of what's sent back by doing the following...

  1. Right-click in a blank area in the Gmail window. In the popup menu pick Inspect
  2. In the window that appears click on the console tab and paste the following...
window.fetch('https://mail.google.com/mail/feed/atom/%5Esq_ig_i_personal', { credentials:'include'}).then(r=>r.text()).then(r=>console.log(r))
  1. You should end up with something like the following, can you send a screenshot of this (feel free to blank out any personal info)...
    Screenshot 2019-05-02 at 09 18 15

I'm not sure I understand correctly here. Do you want me to add my google account to Wavebox a second time? Is it even possible?

In terms of adding the google account a second time, you can do this. Just click the plus button in the bottom-left of the app, pick Gmail, follow the on-screen wizard to sign in and you'll get a second entry for your Gmail which is completely isolated from the first :)

@Cris70

This comment has been minimized.

Copy link
Author

commented May 2, 2019

Hi @Thomas101. I followed your instructions and got a surprise: the server tells me I'm not authorized (see screenshot below). I tried again to reauthorize and to reload, but it still tells me I'm unauthorized.
image

So I followed the second part of your instructions and added my gmail account a second time. And it is actually working correctly, showing no unread messages. Look below: top one is the old account, bottom one is the new one.

image

@Cris70

This comment has been minimized.

Copy link
Author

commented May 3, 2019

@Thomas101, I've been using the newly created account in Wavebox since yesterday. Meanwhile, the old one has been showing the usual "6" badge.
Ten minutes ago, I noticed that the badge had changed to an exclamation mark:

Screenshot_20190504_000135

So I clicked on the old account: it showed a page asking for reauthentication. I did it and - voila - the "6" badge is gone and the account is now correctly synced.

The only difference I noticed, with respect to when I was forcing reauthentication, is that this time it asked me which Google account I wanted to use. I don't remember having to do this step the other times.

Hope this helps!
I'm still keeping the old account in case you need more investigation.

Cris

@Thomas101

This comment has been minimized.

Copy link
Member

commented May 8, 2019

Thanks @Cris70 that's really helpful. I had a few ideas about how I might be able to reproduce this, but none of them seemed to produce a similar behaviour.

I'll see if I can optimistically grab the Unauthorized 401 error and bubble that up in a more useful way. I also need to add some logging utilities into here - needing to a fetch on the console is a pain for anyone coming up against this in the future

Thomas101 added a commit that referenced this issue May 8, 2019

Add addressbar to basic ui. Update wbui-gmail to handle 401 case #1018.…
… Add network log to help with debugging wbui requests #1018

@Thomas101 Thomas101 added this to the Version 4.10.0 milestone May 8, 2019

@Cris70

This comment has been minimized.

Copy link
Author

commented May 8, 2019

@Thomas101 unfortunately today I had problems with the new account, too.
When I started Wavebox I found that the new account was asking for reauth. But when I tried to reauthorize, it was stuck in a loop: look at this animated capture
peekM5LD1Z

I tried again and again without any success. Then I went to the account settings, where I chose "remove credentials" and also (just to be sure) I chose "Clear all browsing data". That allowed me to regain control of the account.

@Thomas101

This comment has been minimized.

Copy link
Member

commented May 9, 2019

@Cris70 how are you connected to the web, are you behind a proxy or vpn server?

Thomas101 added a commit that referenced this issue May 9, 2019

@Thomas101 Thomas101 added in-beta and removed waiting-release labels May 9, 2019

@Thomas101

This comment has been minimized.

Copy link
Member

commented May 9, 2019

@Cris70 4.9.7beta should handle this a little bit better now - let me know if you see the same issue again!

@Cris70

This comment has been minimized.

Copy link
Author

commented May 11, 2019

@Thomas101 I'm directly attached to the web (no proxy or vpn in between).
BTW I'm now on v4.9.8beta. I'll report back to you if I experience any more issues of this type.
Thank you!

@Thomas101

This comment has been minimized.

Copy link
Member

commented May 14, 2019

Thanks @Cris70 these fixes have gone out into the stable version. I'll close this off for now, but if you see it get stuck again just re-comment and I'm happy re-open the issue and take another look :)

@Thomas101 Thomas101 closed this May 14, 2019

@Thomas101 Thomas101 removed the in-beta label May 14, 2019

@Cris70

This comment has been minimized.

Copy link
Author

commented May 14, 2019

Thank you very much for your help @Thomas101 !

@Thomas101

This comment has been minimized.

Copy link
Member

commented May 15, 2019

No worries, that's what we're here for :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.