Bug: Google account logout notifications keep re-appearing

Happy to be a beta beta tester! :)

I'm happy that Jolla is tring to solve this problem. As someone who don't have Facebook and whose XMPP account doesn't work on Jolla (different problem with unknown certificate), I don't have any other mean of communicating via Internet than Google Chat.

Just wanted to update that the fix will be included in the next OS release to be rolled out pretty soon.

FYI: Google acc logout notifications still apoear in 1.0.3.8 and the account status in Settings > Accounts is signed out.. so the bug has not been resolved even if so stated in Release.Notes of.1.0.3.8.

Drat, replied to the wrong answer... @stezz, the "probable fix" doesn't appear to have worked, I'm still getting signed out and needing to re-authenticate with 1.0.3.8. No big deal as email still seems to work, which is the main thing.

I had the same issue in Saapunki, too. Once so far.

Same for me. Before Saapunki it wasn't so often, now it happens at least twice a day.

still suffering from the bug using Tahkalampi :( but not very often hopefully (like once every two/three weeks or so) I am not using Messaging so not related to that: I 'only' sync calendars (3), mails and contacts, using two-way sync, and with a personalized & automatic sync too... And only one google account (plus Jolla account and one de-activated XMPP).

I can confirm this bug is still present on Tahkalampi. Seeing with gTalk activated and deactivated.

What is update3 and is this answer official confirmation that the erroneous notifications of Google acc logouts are to be fixed? As commented above the issue is still present in 1.0.3.8.

jjaone: can you give more information about your particular case? 1.0.3.8 is the update I was referring to. Are you using a normal @gmail.com account, or do you have your own domain (via Google Business etc)? Which services do you have enabled? Does email sync still work? Does gtalk still work?

I have s normal.gmail.com.acc, and have Google acc, Twitter, FB, and Jolla accs setup. The issue has been the same from before 1.0.2.5 tjat once or twice a day the Google acc logout notification is displayed and when going to Settings >.Accounts >.Google it says 'Not signed in'. All the time email sync works, and I can send and receive emails. Havet used GTalk at all, so this has nothing to do with that. Notification can be cleared but then it soon appears again. Same happens if I sign-on to Google then also the notification appears again after some hours (and quite random times). Still present in 1.0.3.8 just as described. This is IMO the original issue report here and has been confiirmed by many.. (see e.g. the first comment by @donaggio).

Maybe it's too early to say, but it does seem to be solved for me: since the update I haven't experienced any disconnection from my Google accounts (one "regular" and one from Google Apps with my company domain). Let's see.

But with just one regular Google acc it has happened to me already several times in two day. Should I now post a new question with this exact description cause seems that all the other variants of this bug have been resolved?

I still do as well, there has been no statement about this being fixed though. Thought about creating a google-account that one can reproduce this with for jolla-testers.

Did you have the same account, like me, a google account that was not a real gmail address, but associated with a mail address external to google? If that's the case, I guess its the problem.

Yup, I do. But weren't we on this earlier before?

Yes I can confirm issue still exists in 1.1.1.27 google account keeps asking for reauthentication about daily. Also it seems to create an additional calendar in calendars at some reauths, not all. So using google calendar as your default calendar is impossible as you never know which google calendar you should add your entries to.

Just adding my two cents, I also have this issue in 1.1.1.27. However, I can't replicate duplicate calendars issue mentioned above. My Google account doesn't use 2 step verification.

Same "not signed in" issue even in Yliaavanlampi 1.1.2.16. Totally random. The odd thing is that syncing still works since I keep receiving emails and calendar entries sync fine both ways.

Yes, in this bug, the flag is usually raised in a case where a software component mistakes a network error (eg, when wifi drops out or something) during sync, as an authentication error from Google. We have investigated some cases where we have error handling and improved them to make sure we deal with network errors correctly, however I can't guarantee that we've found and fixed all of them yet.

Note that while the network error will result in that one single sync failing, subsequent syncs will continue to work correctly, which explains the behaviour you're seeing.

With luck the recent fixes will resolve this issue for you (should be released in the upcoming update), but we will continue to investigate this issue as more information becomes available.

Cheers, Chris.

Effort has been spent recently to try to resolve this issue again. Improved logging was added to various components to try to narrow down the specific circumstances under which the "logged out" flag gets erroneously raised. Also, a bug was fixed in the periodic signon component, where previously it compared error values against an older, deprecated error set (see https://github.com/nemomobile/buteo-sync-plugins-social/commit/47efc63beb2d2c9d95d4e707ef08a0c83a682f77 for that fix), which may fix the issue in some cases.

In general, this one has proven tricky to resolve simply because it's not easily reproducible. People who hit the bug often have identical setups to people who have never seen the bug at all. It's a byzantine bug with no simple solution, but more likely the bug results from complex interactions between a variety of software components which, in some usage patterns, results in the erroneous behaviour.

Rest assured that we're doing what we can to follow up on this one, as more information becomes available.

Cheers, Chris.

@chris.adams Thanks for the info! That's better then nothing. Would be waiting for any solution.

Can you provide details of your account - do you use two-factor authentication, or single-step oauth2? What services do you have enabled? What usage patterns seem to trigger the event (e.g., due to oauth2 access token delegation semantics, tokens will be expired by the server after some period of time, so if your device is offline for multiple days in a row, then this signout behaviour is expected and unavoidable, without using long-expiry (so called "offline") keys)?

Can you provide journal / logs from the device? devel-su journalctl -b | grep CredentialsNeedUpdate should give some useful information for me to track down what is raising the notification, at least.