I believe I encounter this issue with Ubuntu 17.10, which uses "gnome-session 3.26.1-0ubuntu5".
The story, I installed Ubuntu 17.04 back in September 2017 and been using Online Accounts for three Gmail accounts. The email client Evolution was working fine. I then upgraded to Ubuntu 17.10 a couple of days ago. After upgrade, Evolution continued to work by using the configured accounts within Online Accounts. So far so good.
I then realised that Thunderbird was installed during this OS upgrade too. So I uninstalled Thunderbird with "sudo apt purge thunderbird". After that I had this problem that Online Accounts stopped working. The symptom was that all online accounts showed that the login had expired, despite me having re-logged in a couple of times. I then found this bug report and I followed the instructions provided with https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1610944/comments/3, which allowed me to get it working again.
In the light of this, I believe this problem is still present with "gnome-session 3.26.1-0ubuntu5".
I believe I encounter this issue with Ubuntu 17.10, which uses "gnome-session 3.26.1-0ubuntu5".
The story, I installed Ubuntu 17.04 back in September 2017 and been using Online Accounts for three Gmail accounts. The email client Evolution was working fine. I then upgraded to Ubuntu 17.10 a couple of days ago. After upgrade, Evolution continued to work by using the configured accounts within Online Accounts. So far so good.
I then realised that Thunderbird was installed during this OS upgrade too. So I uninstalled Thunderbird with "sudo apt purge thunderbird". After that I had this problem that Online Accounts stopped working. The symptom was that all online accounts showed that the login had expired, despite me having re-logged in a couple of times. I then found this bug report and I followed the instructions provided with https:/ /bugs.launchpad .net/ubuntu/ +source/ gnome-online- accounts/ +bug/1610944/ comments/ 3, which allowed me to get it working again.
In the light of this, I believe this problem is still present with "gnome-session 3.26.1-0ubuntu5".