SessionRestore stopped saving sessions 3 days ago
-
Here is a Beta build which I hope fixes this issue:
https://sweetpproductions.com/products/sessionrestore/SessionRestoreBeta.zipPlease backup your sessions first!
-
@SweetP This beta is removed (404) now. Was it a version before 2.6.8 released? Or something newer? I Would like to test it out, yes, because I even installed manually and back through the store and it still does not work.
If there is a logfile for further debugging I can turn on? Perhaps when SR is activated, it can tell me why it fails to add the session to the backup.
Thanks.
-
@SweetP Well, it DID work. I Then clicked on the "manual save" button and SessionRestore itself crashed, and will not re-start. I noticed that I am running that newer 2.7 version and it briefly said grabbing iCloud Sessions data. I assume that means its saving sessions to the cloud now?
So interesting enough, I have up-to-date sessions saved today, but the program itself now crashes on start. Please advise.
-
@cbrannon a bunch of things.
When I wrote SessionRestore, I had to write some of the code in Objective C, as the Swift calls weren't working for some reason. I rewrote that code in Swift (SessionRestore is written in Swift) as it started causing crashing now for some reason.I added some more checks to help make the Autosave timer more reliable.
And finally, I added code to clear duplicate iCloud sessions, which was maybe causing memory issues and crashing.
-
SessionRestore 2.7.3 only seldom saves sessions for me. Last save was about 23 hours ago. The time before that, about 8 hours earlier. Granted, this is under Mojave so the situation may be different than other reports. Please let me know if there's something you'd like me to do to help track it down if Mojave is still supported.
-
@SweetP I would say it's better. I'm not keeping track of time Safari is up front but sometimes I just leave the Safari screen up for an hour or two yet nothing is saved. So it's unpredictable but, yes, I AM getting occasional saves, which is probably sufficient.
Perhaps when a screen saver kicks in Safari no longer is seen as active?