Ask / Submit

Revision history [back]

click to hide/show revision 1
initial version

posted 2014-02-26 03:55:37 +0200

This is due to two unfortunate bugs which have now been fixed.

The first was that we had set up our application permissions wrongly, and Google recently started enforcing their permissions model more strictly, which meant that our sync adapter hit authorisation errors. The second was that when that occurred, the sync adapter code assumed that the account was invalid, and removed previously-synced contact data from the device.

The first bug has now been fixed via our Google application console, which means if you delete your Google account, wait a couple of minutes, and then re-add your Google account, you should get your contact data again. (You can use systemctl --user stop msyncd.service; SOCIALD_LOGGING_LEVEL=3 devel-su -p msyncd to get more information from the sync adapter on device, in case you hit issues - email me the log at chris dot adams at jolla dot com - thanks!)

The second bug has been fixed in our device software and will be released via update in the near future.

This sort of bug has a drastic effect on the usability of the device for its primary purpose, and I realise that it's inexcusable that this occurred. I'd personally like to thank all of our amazing community members who sent me logs which helped us to track down the root cause of the issues - much appreciated.

Cheers,

Chris.

This is due to two unfortunate bugs which have now been fixed.

The first was that we had set up our application permissions wrongly, and Google recently started enforcing their permissions model more strictly, which meant that our sync adapter hit authorisation errors. The second was that when that occurred, the sync adapter code assumed that the account was invalid, and removed previously-synced contact data from the device.

The first bug has now been fixed via our Google application console, which means if you delete your Google account, wait a couple of minutes, and then re-add your Google account, you should get your contact data again. (You can use systemctl --user stop msyncd.service; SOCIALD_LOGGING_LEVEL=3 devel-su -p msyncd to get more information from the sync adapter on device, in case you hit issues - email me the log at chris dot adams at jolla dot com - thanks!)

The second bug has been fixed in our device software and will be released via update in the near future.

This sort of bug has a drastic effect on the usability of the device for its primary purpose, and I realise that it's inexcusable that this occurred. I'd personally like to thank all of our amazing community members who sent me logs which helped us to track down the root cause of the issues - much appreciated.

Cheers,

Chris.

/edit: important update: it turns out that we still have a problem with our application permissions, which means that after resigning in, the AccessToken will be invalidated within approximately an hour. We are looking into this again.

This is due to two unfortunate bugs which have now been fixed.

The first was that we had set up our application permissions wrongly, and Google recently started enforcing their permissions model more strictly, which meant that our sync adapter hit authorisation errors. The second was that when that occurred, the sync adapter code assumed that the account was invalid, and removed previously-synced contact data from the device.

The first bug has now been fixed via our Google application console, which means if you delete your Google account, wait a couple of minutes, and then re-add your Google account, you should get your contact data again. (You can use systemctl --user stop msyncd.service; SOCIALD_LOGGING_LEVEL=3 devel-su -p msyncd to get more information from the sync adapter on device, in case you hit issues - email me the log at chris dot adams at jolla dot com - thanks!)

The second bug has been fixed in our device software and will be released via update in the near future.

This sort of bug has a drastic effect on the usability of the device for its primary purpose, and I realise that it's inexcusable that this occurred. I'd personally like to thank all of our amazing community members who sent me logs which helped us to track down the root cause of the issues - much appreciated.

Cheers,

Chris.

/edit: important update: it turns out that we still have a problem with our application permissions, which means that after resigning in, the AccessToken will be invalidated within approximately an hour. We are looking into this again.

/edit: should be fixed now.