Cookie, Safari and El Capitan

SweetP

You can restore the BinaryCookies file, but you also need to restart the nsurlstoraged process for any changes to be effective.

Weaselboy

You can restore the BinaryCookies file, but you also need to restart the nsurlstoraged process for any changes to be effective.

Thanks for the tip. That is the piece I was missing.

JerryG

v4.5 is still broken, and can cause cookie loss....

but v4.5.1 has been uploaded for review and restores full full functionality to Cookie. It will be available in around a week i guess.

Sounds great, but where is 4.5.1 for those of us who get it from your site and not the app store?

Thanks

SweetP

here you go:
http://cl.ly/0c293S2o2c2j

i won't officially release it till the MAS version is approved. Otherwise i end up with a full inbox asking why MAS users can't get it yet...

RobertP

Thanks for the update. I am now having a problem with Cookie 4.5.1 closing every time I choose to "Remove" anything from the dropdown menu. It is not crashing...only closing down the app.

JerryG

Thanks for the update. I am now having a problem with Cookie 4.5.1 closing every time I choose to "Remove" anything from the dropdown menu. It is not crashing...only closing down the app.

I found the same problem. Also happens when I quit Safari.

QuattroGam3r

I also noticed Cookie was closing down when quitting Safari, a reboot fixed the issue for me though.

Thank you for fixing the cookie loss issue.

edit: never mind, it started closing again when I quit Safari.

SweetP

Ive just uploaded v4.5.2 to my site, and requested an expedited review for the Mac App Store.

Weaselboy

Ive just uploaded v4.5.2 to my site, and requested an expedited review for the Mac App Store.

Yeah... I'm seeing the same crash on app store 4.5.2. On the plus side though, it no longer corrupts the cookies database.

SweetP

1 step forward. 2 steps back....
i managed to figure out the cookie format, but introduced a memory management bug at the same time.... go figure... hence the crashing

JerryG

1 step forward. 2 steps back....
i managed to figure out the cookie format, but introduced a memory management bug at the same time.... go figure... hence the crashing

Thanks so much for your quick responsiveness in fixing the issues. Cookie is a great program and has become indispensable.

RobertP

Thanks for the quick fixes Russell. Things appear to be back and running smooth. Whew...

SweetP

Cookie 4.5.2 has just been approved, and the update will show in the Mac App Store sometime today.

JBG

Long time lurker and liking the product, just dived in and bought in time for the crash on 10.11.1.

Crash has stopped for me with this update. Thanks.

Still trying out other functions.

SweetP

Ah bad timing....
But happy to hear it's working for you!

It was totally bad timing for me too.
I'd like to apologise to everyone affected by the El Capitan fiasco.
My partner gave birth on the 17th Septemver, so I've been wrestling with Reverse engineering the cookie format, a new baby... And in my infinite stupidity... Also working on Cookie 5.

So I take all the blame, but thanks for hanging in there folks.
Cookie 5 is gonna be awesome, and I'll get a beta out hopefully this week.

JBG

No worries, dipping in here I could see you were working on it. That was the decider to part with loot (as well as it did what it said on the tin).

I had tried the trial version pre crash. And I am on the beta version of OS.

Congrats on the little one.

Weaselboy

My take on all this is people are fairly patient as long as you acknowledge the problem and are working on it, like you communicated here over the last weeks. Nicely handled.

Congrats on the baby!

RNKLN

Hi,
When reading this forum post it looks like 4.5.2 is supposed to solve all problems. Not in my case. Cookie keeps quitting spontaneously, as soon as i use the periodic auto delete of certain cookies (Every: X minutes when Browser is Open).

What could be special in my settings?

I'm on El Capitan (10.11.1) with Cookies 4.5.2.

SweetP

V4.5.3 is actually the latest stable version. But it is still waiting to be reviewed for the Apo Store.

RNKLN

So a matter of days. I can live with that (assuming it solves the issue, and even then...)