inbasic
Notifier does not delete or mark emails as read [v1.1.9]
This has happened in the past, in older versions, and it keeps happening. Clicking the "delete" button or the "Mark as read" button does not do what it should.
I am using "Notifier for Gmail" version 1.1.9, on Google Chrome browser Version 131.0.6778.70 (Official Build) (64-bit).
Can confirm that this also happens to me for some time, Google Chrome version Version 130.0.6723.117, extension version is 1.1.9
Firefox here. I confirm it's happening, but only for private domain. For accounts on gmail.com everything works flawlessly, but in a week or so, my work gmail account hosted on private domain refreshes correctly, shows the mail, but cannot delete, mark as read or archive from the extension popup window.
Does this still occur if you open the account in a browser tab? Occasionally, the extension may not recognize the "at" parameter until the account is opened at least once during the session.
I confirm it's happening, but only for private domain.
What is the URL of the Gmail interface for this account?
obfuscated And I can confirm that even with the account opened in a tab, the extension still refuse to archive, etc.
Even if Gmail is open and logged in, it still happens.
El lun, 18 de nov. de 2024 06:57, InBasic @.***> escribió:
Does this still occur if you open the account in a browser tab? Occasionally, the extension may not recognize the "at" parameter until the account is opened at least once during the session.
— Reply to this email directly, view it on GitHub https://github.com/inbasic/ignotifier/issues/692#issuecomment-2482690994, or unsubscribe https://github.com/notifications/unsubscribe-auth/BL33HBEKHBVSULTKYZ3RMG32BHB2HAVCNFSM6AAAAABR3TEFACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBSGY4TAOJZGQ . You are receiving this because you authored the thread.Message ID: @.***>
What is shown in the addressbar of Gmail for your custom domain? e.g.: https://mail.google.com/mail/u/0
the same as always:
https://mail.google.com/mail/u/0/
El lun, 18 de nov. de 2024 06:58, InBasic @.***> escribió:
I confirm it's happening, but only for private domain.
What is the URL of the Gmail interface for this account?
— Reply to this email directly, view it on GitHub https://github.com/inbasic/ignotifier/issues/692#issuecomment-2482694183, or unsubscribe https://github.com/notifications/unsubscribe-auth/BL33HBERGOLP7TNBJUGZ7MT2BHB53AVCNFSM6AAAAABR3TEFACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBSGY4TIMJYGM . You are receiving this because you authored the thread.Message ID: @.***>
In my case I have configured that same URL
https://mail.google.com/mail/u/0
In all these years I have never used a different URL than that in the configuration.
Excuse my ignorance, what is the difference between /u/0 and /u/4 ?
El lun, 18 de nov. de 2024 08:31, InBasic @.***> escribió:
What is shown in the addressbar of Gmail for your custom domain? e.g.: https://mail.google.com/mail/u/0
— Reply to this email directly, view it on GitHub https://github.com/inbasic/ignotifier/issues/692#issuecomment-2482911193, or unsubscribe https://github.com/notifications/unsubscribe-auth/BL33HBCJSF4SP63L77KC5TL2BHM33AVCNFSM6AAAAABR3TEFACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBSHEYTCMJZGM . You are receiving this because you authored the thread.Message ID: @.***>
I understand, thanks. The funny thing is that I manage 2 Gmail accounts with the same extension and the URL in the configuration has always been /u/0 by default and it had worked like that until this problem came back.
El lun, 18 de nov. de 2024 09:21, 4javier @.***> escribió:
It's just because I have many gmail accounts. That's the fourth one.
— Reply to this email directly, view it on GitHub https://github.com/inbasic/ignotifier/issues/692#issuecomment-2483027825, or unsubscribe https://github.com/notifications/unsubscribe-auth/BL33HBF7YTQIG7LY66ZZZRD2BHSUJAVCNFSM6AAAAABR3TEFACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBTGAZDOOBSGU . You are receiving this because you authored the thread.Message ID: @.***>
Since i don't have access to a custom domain on Google Workspace, I cannot debug this. If anybody can create a temp email for me, I'll take a look.
I've also experienced this in firefox, although I can only confirm an issue with Mark As Read as that's all I ever use, and I'm using a public gmail address. Visiting the inbox was fine and displaying new emails was also fine.
In my case, I did attempt to debug the issue, the extension was failing when calling JSON.parse in I think core.js as it was getting non json text. I think this was the text, but tbh I'm not quite sure as it doesn't seem to resemble any particular mark up I'm familiar with, but potentially before then the extension may have some transformation on it prior to this point that garbled it up.
<scr "https://mail.google.com/mail/u/0/spreauth"
Following that url manually in the browser, seemed to force some kind of re-authentication, but after I did it, the issue went away and the button was functional again, which prevented me from debugging any further.
Thanks. I followed the same link (but for the only troubled account of mine, 4 instead of 0), it retriggered the authentication, and now archive button works again. For me, this peculiar 2factor auth flow was something new on Gmail, so maybe their auth system changed recently and brought the issue with it.
I've also experienced this in firefox, although I can only confirm an issue with Mark As Read as that's all I ever use, and I'm using a public gmail address. Visiting the inbox was fine and displaying new emails was also fine.
In my case, I did attempt to debug the issue, the extension was failing when calling JSON.parse in I think core.js as it was getting non json text. I think this was the text, but tbh I'm not quite sure as it doesn't seem to resemble any particular mark up I'm familiar with, but potentially before then the extension may have some transformation on it prior to this point that garbled it up.
<scr "https://mail.google.com/mail/u/0/spreauth"Following that url manually in the browser, seemed to force some kind of re-authentication, but after I did it, the issue went away and the button was functional again, which prevented me from debugging any further.
The provided link did not work by itself for me. I had to add the accounts to my Gmail app on my phone. When using the link, I had to accept the authentication on my phone. This fixed the issue for me. If I used the phone message for authentication, it did not work.
