Socialite stuck at refreshing Google Reader, Twitter and every other thing..
Derrick Tan
via web
Hi,
I have been having this problem with Socialite ever since I tested it. Every time when I do a fresh installation of Socialite, everything works smoothly and fast. But after a couple of restart, Socialite will just get start at trying to refresh Google Reader and every other accounts I got on it. The circle that shows that it is refreshing just keeps spinning and won't stop. And while it is doing that, I can't view any of the new news from the RSS feed. This is solve by clicking on it, click on another news, and click back.
I am at a lost as to what is causing this problem.
I am using Snow Leopard 10.6.4 on an Intel i5
Cheers,
Derrick
Comments are currently closed for this discussion. You can start a new one.
2 Posted by David on 30 Aug, 2010 08:01 AM
I'm experiencing the same issue. Using the latest release of Socialite (1.2.2)
3 Posted by Steve Robinson on 30 Aug, 2010 02:24 PM
I had the same problem. I tried deleting my services and recreating them, to no avail. the only solution I found was:
1. Quit Socialite
2. Delete the Socialite.sqlite database in /Users/<>/Library/Application Support/Socialite/
3. Start Socialite and recreate services and settings.
Not a great solution, but I'm up and running again.
4 Posted by Derrick Tan on 30 Aug, 2010 02:30 PM
That's what I did as well but that's not a very good solution if we have to keep doing that. Hope they will be able to figure out what's wrong and solve this problem.
5 Posted by Chris Zumbrunn on 01 Sep, 2010 10:20 AM
Same problem here. I'm assuming that just dumping the db and having to reconfigure all the accounts can not be the solution, since the same thing could happen again. I'll wait it out to see if/how it can be fixed. So, can't use Socialite anymore for now.
Support Staff 6 Posted by Nik Fletcher on 01 Sep, 2010 10:35 AM
Hi Guys
Thanks for your message. We're continuing to look into this, and a future update to Socialite will have a re-worked database schema to fix this. In the mean time, the only solution would be to a) minimise the use of Smart Folders (the edge cases for these seem to be causing a number of issues) and b) lower the content limit on containers to several days. We're working on ensuring that Socialite is far more robust in the future to resolve this.
Please let me know if I can be of any further assistance.
Kind regards,
Nik
-- Nik Fletcher
Support & QA Manager, Realmac Software
Our support team are in the office between 9am and 5pm UK time, Monday to Friday, and we aim to answer all requests within one business day.
7 Posted by Chris Zumbrunn on 01 Sep, 2010 11:02 AM
Ok, I'll keep the database around that I have to dump. Let me know if you would like to check for something inside of it. For what it's worth, storing the account settings separate from the cached content data would probably make sense.
Support Staff 8 Posted by Nik Fletcher on 01 Sep, 2010 11:18 AM
Hi Chris
Whilst we store the credentials in the keychain, the unique identifiers that link each account to its credentials is stored in the database. Due to the way that authentication occurs (we aren't normally using usernames/passwords to access data) there's timestamps, token signatures and other crazy things that mean we can't always just 're-use' credentials!
Please let me know if I can be of any further assistance.
Kind regards,
Nik
-- Nik Fletcher
Support & QA Manager, Realmac Software
Our support team are in the office between 9am and 5pm UK time, Monday to Friday, and we aim to answer all requests within one business day.
Nik Fletcher closed this discussion on 06 Sep, 2010 07:53 AM.