Socialite stopped saving changes today.
Loren finkelstein
via web
Socialite isn't saving changes any more. If I have 500 unread messages, and I mark them all as read and then quit and relaunch, they are all still marked as unread. This is happening on 2 separate machines. 1 running Lion and one running Snow Leopard.
I tried deleting the database, the cache and the preferences, as well as repairing permissions. No luck
Any ideas???
Thanks,
Loren
Showing the most recent page of comments. View the first page
Comments are currently closed for this discussion. You can start a new one.
Support Staff 32 Posted by Jacob Gorban on 07 Feb, 2012 10:39 AM
Hello, Michael.
I definitely know Boinx software. Moreover, I know Oliver and Florian personally. I met and spend quite some time with Florian at MacTech Conference last November. We stayed in contact after that. You can ask him about me. I met Oliver at Macworld Exoi 2011 (not this one, the previous).
Now, as I think that I know what the id of the event was that wasn't saved, let's see if you can get its information from Facebook.
Try to go to the following URL:
https://developers.facebook.com/tools/explorer?method=GET&path=...
100000147864142_1565948 is the Facebook ID of the event that wasn't completely initialized and didn't pass Core Data's model validation, thus it wasn't saved.
This should take you the dev's site of Facebook and try to get the data for this specific event id, which I think is the cause. To me, when I try it, it returns 'false', probably because I simply don't have the authorization to access this data. But I believe that if you log in with your own Facebook account, it'll show you the JSON for this response. If it will show and it's nothing private, you can post it here. If not, you can email me.
There's also a more detail debug logging available, when pressing Cmd-Alt-Control-S. A new window will open with a more detailed log.
When I asked about the version of Socialite, I meant the one that showed the message about an incompatible database model. I asked this because the betas have a new Core Data model, so they migrated the database (that why I asked to back it up first). If you saw this message on 1.3.9 after running the beta, then it's ok. If some other use-case, then it's probably not ok.
Jacob.
33 Posted by Michael Ehrmann on 07 Feb, 2012 11:42 AM
Hi Jacob,
I created an access token with all permissions available and tried to get the event id in the graph API explorer. As for you this event just returns false.
However the first part of this ID seems to be the ID of a friend, so could it be it is an event of a friend?
-- Michael
On 07.02.2012, at 11:39, Jacob Gorban wrote:
>
> Please reply above this line
Support Staff 34 Posted by Jacob Gorban on 07 Feb, 2012 11:56 AM
Yes, that means that it's an event of that friend. But I can't know which type.
It's possible that the user deleted this event, though, and that's why it returns false.
If the problem with Facebook not saving still persists, do you get anything in the debug log (the one opened with Cmd-Alt-Command-S? Press this key press right when Socialite starts so that the whole Facebook refresh process will go through this log. Then, when refresh is finished, switch to some other application and get back to Socialite after about a minute. You should see in the debug log if it saved or not. If not saved, you'll see the Core Data errors.
Perhaps some helpful information will also in the part of the log that was during refresh. And then, maybe there'll be an exception in console, like you previously saw.
Can you run this check?
Jacob.
35 Posted by Michael Ehrmann on 07 Feb, 2012 01:29 PM
Sure. Here is the Socialite log, I just removed my access token from the URLs:
[2012-02-07 13:16:04 +0000] connectionDidFinishLoading: https://api.facebook.com/restserver.php?access_token=XXXMyAccessTocenXXX&v=1.0&method=facebook.fql.query&query=SELECT%20uid%2C%20name%2C%20is_blocked%20FROM%20user%20WHERE%20uid%20IN%20%28SELECT%20owner%20FROM%20album%20WHERE%20owner%20IN%20%28SELECT%20uid2%20FROM%20friend%20WHERE%20uid1%3D1327145674%29%20ORDER%20BY%20modified_major%20DESC%20LIMIT%20500%29&format=JSON&call_id=14
[2012-02-07 13:16:04 +0000] <EBNetworkManager: 0x18bff90> Running: 0 (u), 1 (l); Waiting: 0; Limit: 10
[2012-02-07 13:16:04 +0000] connection: <NSURLConnection: 0xd3df5b0, https://api.facebook.com/restserver.php?v=1.0&access_token=XXXMyAccessTocenXXX&call_id=15&query=SELECT%20pid%2C%20aid%2C%20owner%2C%20src_small%2C%20src_big%2C%20src%2C%20link%2C%20caption%2C%20created%20FROM%20photo%20WHERE%20aid%20IN%20%28SELECT%20aid%20FROM%20album%20WHERE%20owner%20IN%20%28SELECT%20uid2%20FROM%20friend%20WHERE%20uid1%3D1327145674%29%20ORDER%20BY%20modified_major%20DESC%20LIMIT%20300%29%20ORDER%20BY%20created%20DESC%20LIMIT%20500&format=JSON&method=facebook.fql.query> url:<NSMutableURLRequest https://api.facebook.com/restserver.php?v=1.0&access_token=XXXMyAccessTocenXXX&call_id=15&query=SELECT%20pid%2C%20aid%2C%20owner%2C%20src_small%2C%20src_big%2C%20src%2C%20link%2C%20caption%2C%20created%20FROM%20photo%20WHERE%20aid%20IN%20%28SELECT%20aid%20FROM%20album%20WHERE%20owner%20IN%20%28SELECT%20uid2%20FROM%20friend%20WHERE%20uid1%3D1327145674%29%20ORDER%20BY%20modified_major%20DESC%20LIMIT%20300%29%20ORDER%20BY%20created%20DESC%20LIMIT%20500&format=JSON&method=facebook.fql.query>
[2012-02-07 13:16:04 +0000] <EBNetworkManager: 0x18bff90> Running: 0 (u), 2 (l); Waiting: 0; Limit: 10
[2012-02-07 13:16:04 +0000] Deallocing <EBFacebookFQLAction: 0xd3f8540>
[2012-02-07 13:16:12 +0000] connectionDidFinishLoading: https://api.facebook.com/restserver.php?method=facebook.stream.get&call_id=9&access_token=XXXMyAccessTocenXXX&v=1.0&start_time=1327595060&viewer_id=1327145674&metadata=profiles&filter_key=nf&limit=1000&format=JSON
[2012-02-07 13:16:12 +0000] <EBNetworkManager: 0x18bff90> Running: 0 (u), 1 (l); Waiting: 0; Limit: 10
[2012-02-07 13:16:12 +0000] Deallocing <EBFacebookStreamAction: 0xc55a6c0>
[2012-02-07 13:16:13 +0000] connectionDidFinishLoading: https://api.facebook.com/restserver.php?v=1.0&access_token=XXXMyAccessTocenXXX&call_id=15&query=SELECT%20pid%2C%20aid%2C%20owner%2C%20src_small%2C%20src_big%2C%20src%2C%20link%2C%20caption%2C%20created%20FROM%20photo%20WHERE%20aid%20IN%20%28SELECT%20aid%20FROM%20album%20WHERE%20owner%20IN%20%28SELECT%20uid2%20FROM%20friend%20WHERE%20uid1%3D1327145674%29%20ORDER%20BY%20modified_major%20DESC%20LIMIT%20300%29%20ORDER%20BY%20created%20DESC%20LIMIT%20500&format=JSON&method=facebook.fql.query
[2012-02-07 13:16:13 +0000] <EBNetworkManager: 0x18bff90> Running: 0 (u), 0 (l); Waiting: 0; Limit: 10
[2012-02-07 13:16:13 +0000] Deallocing <EBFacebookFriendsPhotosAction: 0xc55de20>
[2012-02-07 13:16:13 +0000] Deallocing <EBFacebookFQLAction: 0xd3dec40>
[2012-02-07 13:16:18 +0000] After recovery: NO
[2012-02-07 13:16:18 +0000] Fatal error occurred=Error Domain=NSCocoaErrorDomain Code=1570 "Property/serviceInfo/Entity/EventIdentifier is a required value." UserInfo=0xd4f7960 {NSValidationErrorObject=<EBEventIdentifier: 0xacb9250> (entity: EventIdentifier; id: 0xacb9290 <x-coredata:///EventIdentifier/tB997056F-3C3D-4B70-8AE4-D3CE12451FBD3036> ; data: {
containers = (
);
date = 2012-01-26 17:52:33 +0000;
event = nil;
identifier = "100000147864142_1565948";
serviceInfo = nil;
}), NSValidationErrorKey=serviceInfo, NSLocalizedDescription=Property/serviceInfo/Entity/EventIdentifier is a required value.}, user info={
NSLocalizedDescription = "Property/serviceInfo/Entity/EventIdentifier is a required value.";
NSValidationErrorKey = serviceInfo;
NSValidationErrorObject = <EBEventIdentifier: 0xacb9250> (entity: EventIdentifier; id: 0xacb9290 <x-coredata:///EventIdentifier/tB997056F-3C3D-4B70-8AE4-D3CE12451FBD3036> ; data: {
containers = (
);
date = 2012-01-26 17:52:33 +0000;
event = nil;
identifier = "100000147864142_1565948";
serviceInfo = nil;
});
}
And there is nothing on the console.
On 07.02.2012, at 12:56, Jacob Gorban wrote:
>
> Please reply above this line
Support Staff 36 Posted by Jacob Gorban on 07 Feb, 2012 04:10 PM
Hi again, Michael.
Please try try the following build:
http://dl.apparentsoft.com//beta/Socialite_1.4.0b6.zip
Do the procedure with the log, as previously.
Take a look at the log. If there's a new line with text "WARNING: Removing bad eventIdentifier" then I hope the issue is fixed (obviously, check if Socialite actually saves the data).
I've found one place in the photo fetching code where a stale object could be created if the whole photo object could not be initialized, for some reason.
Jacob.
37 Posted by Michael Ehrmann on 07 Feb, 2012 04:20 PM
Hi Jacob,
the beta seems to fix the issue! Great :)
this is in the log file:
[2012-02-07 16:14:15 +0000] <EBNetworkManager: 0xd6b39b0> Running: 0 (u), 0 (l); Waiting: 0; Limit: 10
[2012-02-07 16:14:15 +0000] WARNING: Removing bad eventIdentifier <EBEventIdentifier: 0xd9058f0> (entity: EventIdentifier; id: 0xd905930 <x-coredata:///EventIdentifier/t2ABB6026-6B57-4539-B8BB-22540C8C2DCE3328> ; data: {
containers = (
);
date = "2012-01-26 17:52:33 +0000";
event = nil;
identifier = "100000147864142_1565948";
serviceInfo = nil;
}) because no data extracted for photo http://www.facebook.com/photo.php?fbid=364804026867856&set=a.121291977885730.20591.100000147864142&type=1
[2012-02-07 16:14:16 +0000] Deallocing <EBFacebookFriendsPhotosAction: 0xeb62520>
[2012-02-07 16:14:16 +0000] Deallocing <EBFacebookFQLAction: 0x115664c0>
[2012-02-07 16:14:39 +0000] Performing content limitation
[2012-02-07 16:14:39 +0000] Content limitation will be performed for 51 containers
[2012-02-07 16:14:39 +0000] Content limitation finished
[2012-02-07 16:14:40 +0000] Saved database
Database is saved now again.
Greetings, Michael
On 07.02.2012, at 17:10, Jacob Gorban wrote:
>
> Please reply above this line
38 Posted by shahrooz on 07 Feb, 2012 04:51 PM
Looks like others were having success getting read items to stay read between sessions with the new beta. Gave it a shot, and got this error during database upgrade:
Could Not Load Database
It seems that the Socialite database is not compatible with this version of the application, please check if there is a later version available. If you continue to have problems contact support.
What should I do? Download an older version? Try again with the new beta?
Support Staff 39 Posted by Jacob Gorban on 07 Feb, 2012 04:59 PM
Michael, I wonder if you can see the image at that URL:
http://www.facebook.com/photo.php?fbid=364804026867856&set=a.12...
If yes, I wonder what's so strange with this image.
I'd prefer to find a way to load the image into Socialite, in case there's some trivial issue with its metadata than to drop it.
Jacob.
Support Staff 40 Posted by Jacob Gorban on 07 Feb, 2012 05:00 PM
Shahrooz, what beta file did you download?
Did you try the latest one at: http://dl.apparentsoft.com//beta/Socialite_1.4.0b6.zip
Did you back up your old database? You should've, for these cases. If yes, maybe try to restore it and run b6 again.
Jacob.
41 Posted by shahrooz on 07 Feb, 2012 05:02 PM
Yes, I tried the latest Socialite_1.4.0b6 and I almost always do a backup, but slipped this time. Will I need to do a fresh install at this point?
Where are automated/manual database/backups usually stored?
Support Staff 42 Posted by Jacob Gorban on 07 Feb, 2012 05:16 PM
Shahrooz,
Socialite does a backup during migration from older version of databases to newer.
See if the folder at [your home]/Library/Application Support/Socialite has a file with _Backup in it.
Jacob.
43 Posted by Michael Ehrmann on 07 Feb, 2012 05:34 PM
The image is broken or there is no image for me with that link, however from timeline I can see he reposted the image. (At least one with the status message)
So I guess the first version we are trying to access has been deleted but is still in the FB Graph data.
Michael
On 07.02.2012, at 17:59, Jacob Gorban wrote:
>
> Please reply above this line
44 Posted by shahrooz on 07 Feb, 2012 05:41 PM
Sweet!!!
Socialite_Migrated.sqlite
Socialite_Backup.sqlite
Socialite.sqlite
Which backup file do I rename and what do we rename it to before restarting the app?
Support Staff 45 Posted by Jacob Gorban on 07 Feb, 2012 11:02 PM
Socialite.sqlite is the one that Socialite uses to run.
_Backup is the one that Socialite was using before the migration, i.e. before you used the beta.
You can try migration again by copying Socialite_Backup.sqlite over Socialite.sqlite.
Jacob.
46 Posted by shahrooz on 08 Feb, 2012 05:56 PM
I changed the name of Socialite.sqlite - and then attempted opening socialite with Socialite_Backup.sqlite renamed to Socialite.sqlite, which gave me the same error Could Not Load Database
It seems that the Socialite database is not compatible with this version of the application, please check if there is a later version available. If you continue to have problems contact support.
When I tried the same with Socialite_Migrated.sqlite renamed to Socialite.sqlite, Socialite doesn't seem to use that renamed file and instead creates a new Socialite.sqlite file both with the same name in the same location, which I didn't think was possible with the file system, but alas happened and asked to set everything up from scratch.
Any suggestions?
Support Staff 47 Posted by Jacob Gorban on 08 Feb, 2012 06:34 PM
Shahrooz,
I guess that you didn't rename correctly the second time. Indeed, two files in the same folder can't have the same name.
I'm afraid if perhaps you migrated twice because of the various copies and the backup or migrated files are not the original ones?
Can you continue from the new database or was there any data that you can't restore, like RSS feeds?
If you have to restore RSS feeds from the old database, will you zip and send me that Backup file?
Jacob.
48 Posted by shahrooz on 08 Feb, 2012 07:04 PM
Got the backup to work, by installing 1.3.9 ... but it seems to be a very old backup, because I haven't used Socialite for Digg or Google Reader in years. Also, what I do use it for, Facebook, Twitter and Smart Folders I've customized aren't there.
Even if I remove all services and migrate to 1.4b6:
Support Staff 49 Posted by Jacob Gorban on 08 Feb, 2012 09:17 PM
Shahrooz.
1.4.0b5 is ok, I didn't update the version in about in b6 download, since it was a rather small update.
If your database is years old (you can probably see it in the date), then perhaps indeed it won't migrate. Too bad there's no back up from latest migration, for some reason.
Jacob.
50 Posted by shahrooz on 09 Feb, 2012 03:47 PM
The plus side to having lost all my custom smart folders is that starting from scratch uses a lot less memory :)
Is there a way to export smart folders and re-import them from time to time to drop memory usage?
Might want to check into why the migration didn't backup the latest version in use - as the backup seems to be a very old version.
Support Staff 51 Posted by Jacob Gorban on 10 Feb, 2012 07:04 AM
No, there's no way to export or import smart folders.
52 Posted by ruud on 10 Feb, 2012 08:19 AM
Jacob,
Bit of a late reaction, but for me, it works again. I started from scratch and just added Facebook and Socialite remembers my read items. Thanks.
Ruud
53 Posted by Joel Marcey on 15 Feb, 2012 04:11 PM
Just as a data point, I was having the same issue re: items marked as read becoming unread again on relaunch. Also, new searches wouldn't be saved either. This was with 1.3.x. The 1.4b6 seems to have solved this issue.
54 Posted by Chris on 15 Feb, 2012 10:18 PM
I was having the same issue. Installing 1.4.0b6 solved it. Thank you. That was so bloody irritating.
55 Posted by Jay on 16 Feb, 2012 03:37 AM
Another user here... had the same issue with same version. installed 1.40b6 over the top. All good now, but the font change seems very weird. Is it just a change in anti-aliasing, something else, or just me?
56 Posted by Brendon on 16 Feb, 2012 05:56 AM
Yip. The download from the 1.4.0b6 link above has done the job for me too. Although when I click on "About Socialite" it says that it's Version 1.4.0b5 (7722) (and the copyright is 2 years out of date!)
Support Staff 57 Posted by Jacob Gorban on 16 Feb, 2012 08:57 AM
Jay, there are no font changes in 1.4.0b6.
By the way, everyone, there's a release of 1.4.0 available now.
Jacob.
58 Posted by Jay on 18 Feb, 2012 03:37 AM
Hi Jacob,
Not a font change, but an anti-aliasing change. It may be subtle, but it's crystal clear to me. See two screenshots.
59 Posted by Jay on 18 Feb, 2012 03:37 AM
And 1.4
60 Posted by Jay on 18 Feb, 2012 03:39 AM
Looks like you've found this issue in another thread.
Sandy closed this discussion on 24 Apr, 2012 07:51 AM.