-
Notifications
You must be signed in to change notification settings - Fork 7
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
Constantly asking for access #58
Comments
Hi Bill, unfortunately I really have no idea about it. I remember another user having the very same issue (#47). My guess is that Google is gradually changing something on their side, probably updating old accounts and aligning them to their new standards? It would be nice to hear from other people too. MZ |
Hi Marco, I did look around for an existing topic, but somehow I missed this one. Is there any reason we have to use testing app credentials? What would happen if we tried a different type of app credential? I guess if we have to use testing app credientials, then I'll just have to iive with it. Thanks, |
It is unfortunate, but I think I will be moving back to Cardbook. No problems there with constantly asking for access. Bill |
Hi Bill, sorry for the late reply. The "testing" mode is required because, otherwise, You would have to pass through additional verification steps (including a YouTube video). Thanks, |
I've been experiencing the same issue where I keep getting asked to allow access. As far as I know, it's only been the last few days I've seen it. |
Hello, Same problem here. The login is requested very regularly. I'd say about once or twice a week... Another Google mystery... ^^' |
This is something I really don't have an answer for. MZ |
I have been seeing this issue as well. It's been several months now. Sometimes all I have to do is to allow access directly from the pop-up. But sometimes it's a different pop-up, and I have to go grab my phone and allow access and tap the same number that is displayed on the pop-up. I have to do this every few days. |
Recently I have started getting the following pop-up quite frequently ( Since Google-4-TbSync version 0.6.0 was released I think) .
I have made no changes to anything. Previously I had been running Google-4-TbSync without problems since it first was released as a beta. I allow the access and then it pops up again after a few days. Is this a bug in the latest release? Any ideas how to get rid of this error?
I am on Thunderbird 115.3.1 and Google-4-TbSync 0.6.0.
Thanks,
Bill
The text was updated successfully, but these errors were encountered: