SessionRestore stopped saving sessions 3 days ago
-
@SweetP ok, and the verdict isβ¦.YAY! It loads again.
I started SR and fine, loaded Safari, it immediately loaded iCloud data, fine. Then I saved session from both the app, and Safari, and still fine.
So it checks out. -
@rhawk301 great!
finally
-
@SweetP It seems to be working for me, too. Thanks! Such a huge relief.
I'm curious what the issue was.
--Chris
-
@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.
-
@big SessionRestore will only save sessions when Safari is the active app. So if you have it open but sitting in the background it won't save, but it should pick up where it left off and start saving again when you activate Safari.
-
@SweetP Thanks, Russell. Unfortunately, I can leave Safari upfront for hours yet the session won't save. It's been over 22 hours since the last save. I'll try not to restart anything in case there's info you need.
-
@SweetP A session was just saved, 24 hours and 5 minutes since the last one!
-
@big hmm, hopefully it starts saving correctly again for you
-
@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?